Re: subscription/t/010_truncate.pl failure on desmoxytes in REL_13_STABLE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: subscription/t/010_truncate.pl failure on desmoxytes in REL_13_STABLE
Date: 2021-06-24 17:54:59
Message-ID: 2673480.1624557299@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
> On Tue, Jun 22, 2021 at 6:54 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> BTW, the reason that the walsender is still showing its "query" as
>> "SELECT pg_config..." is that pre-v14 versions don't update the
>> reported query for replication commands, only plain-SQL commands.
>> I recall that we fixed that in HEAD awhile ago; should we consider
>> back-patching something for it?

> I think it would be great if we can do that. Analyzing such failures
> and in general for replication errors that will be a nice improvement
> and make the jobs of many people a bit easier.

Checking the git history, this was fixed in f560209c6, which also
included some other mostly-cosmetic cleanup. I'm inclined to
propose back-patching that whole commit, rather than allowing the
code in exec_replication_command() to diverge in different branches.
It looks like it applies cleanly as far back as v10. Maybe something
could be done for 9.6 as well, but since that branch is so close to
EOL, I doubt it's worth spending extra effort on it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2021-06-24 18:13:55 Re: Added schema level support for publication.
Previous Message Matthias van de Meent 2021-06-24 16:21:45 Re: Iterating on IndexTuple attributes and nbtree page-level dynamic prefix truncation