pgsql: Fix valgrind issue in pgoutput.c. - Mailing list pgsql-committers

From Amit Kapila
Subject pgsql: Fix valgrind issue in pgoutput.c.
Date
Msg-id E1lu57L-00069k-TY@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix valgrind issue in pgoutput.c.

We use a tuple conversion map for partitions when replicating using an
ancestor's schema to convert tuples from partition's type to the
ancestor's. Before this map got initialized, we were processing
invalidation messages which access this map.

This issue happens only in version 13 as in HEAD we already have a code
that initializes each relation entry before we can process any
invalidation message. This issue is introduced by commit d250568121 in
version 13.

Reported-by: Tom Lane, as per buildfarm meber skink
Author: Amit Langote
Reviewed-by: Dilip Kumar, Amit Kapila
Discussion: https://www.postgresql.org/message-id/648020.1623854904@sss.pgh.pa.us

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/357cb8f07f95665ea533ff534821c22c35b01288

Modified Files
--------------
src/backend/replication/pgoutput/pgoutput.c | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Update plpython_subtransaction alternative expected files
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Update plpython_subtransaction alternative expected files