Fix fetching default toast value during decoding of in-progress transactions.
authorAmit Kapila <akapila@postgresql.org>
Mon, 7 Oct 2024 09:23:18 +0000 (14:53 +0530)
committerAmit Kapila <akapila@postgresql.org>
Mon, 7 Oct 2024 09:23:18 +0000 (14:53 +0530)
commit8175a7d11f70589f6b44e28a8dd804f7542d0bbf
tree78d0d22f7449d19700601a6ccf56a417194a18e6
parentaef75219cc221cd4990eaec7d4213d85ed945069
Fix fetching default toast value during decoding of in-progress transactions.

During logical decoding of in-progress transactions, we perform the toast
table scan while fetching the default toast value for an attribute. We
forgot to initialize the flag during this scan to indicate that the system
table scan is in progress. We need this flag to ensure that during logical
decoding we never directly access the tableam or heap APIs because we check
for concurrent aborts only in systable_* APIs.

Reported-by: Alexander Lakhin
Author: Takeshi Ideriha, Hou Zhijie
Reviewed-by: Amit Kapila, Hou Zhijie
Backpatch-through: 14
Discussion: https://postgr.es/m/18641-6687273b7f15269d@postgresql.org
contrib/test_decoding/expected/stream.out
contrib/test_decoding/sql/stream.sql
src/backend/access/index/genam.c