pgsql: Fix valgrind issue in pgoutput.c.

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix valgrind issue in pgoutput.c.
Date: 2021-06-18 03:24:27
Message-ID: E1lu57L-00069k-TY@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2021-06-18 04:57:03 pgsql: Update plpython_subtransaction alternative expected files
Previous Message Tom Lane 2021-06-17 22:06:28 Re: pgsql: Update plpython_subtransaction alternative expected files