diff options
| author | Amit Kapila <akapila@postgresql.org> | 2020-09-16 07:45:44 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2020-09-16 07:45:44 +0530 |
| commit | 69bd60672af63eaa8b19cdcea175df5ff172e80e (patch) | |
| tree | 856f37db90e426cb2159742847adc716f3b6fd13 /src/backend/tcop/postgres.c | |
| parent | 19c60ad69a91f346edf66996b2cf726f594d3d2b (diff) | |
| download | postgresql-69bd60672af63eaa8b19cdcea175df5ff172e80e.tar.gz postgresql-69bd60672af63eaa8b19cdcea175df5ff172e80e.zip | |
Fix initialization of RelationSyncEntry for streaming transactions.
In commit 464824323e, for each RelationSyncEntry we maintained the list
of xids (streamed_txns) for which we have already sent the schema. This
helps us to track when to send the schema to the downstream node for
replication of streaming transactions. Before this list got initialized,
we were processing invalidation messages which access this list and led
to an assertion failure.
In passing, clean up the nearby code:
* Initialize the list of xids with NIL instead of NULL which is our usual
coding practice.
* Remove the MemoryContext switch for creating a RelationSyncEntry in dynahash.
Diagnosed-by: Amit Kapila and Tom Lane
Author: Amit Kapila
Reviewed-by: Tom Lane and Dilip Kumar
Discussion: https://postgr.es/m/904373.1600033123@sss.pgh.pa.us
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions