Re: subscription/t/010_truncate.pl failure on desmoxytes in REL_13_STABLE - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: subscription/t/010_truncate.pl failure on desmoxytes in REL_13_STABLE
Date
Msg-id CAA4eK1Kft05mwNuZbTVRmz8SNS3r+uriuCT8DxL5KJy5btoS-A@mail.gmail.com
Whole thread Raw
In response to Re: subscription/t/010_truncate.pl failure on desmoxytes in REL_13_STABLE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: subscription/t/010_truncate.pl failure on desmoxytes in REL_13_STABLE
List pgsql-hackers
On Tue, Jun 22, 2021 at 6:54 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Thomas Munro <thomas.munro@gmail.com> writes:
> > On Tue, Jun 22, 2021 at 10:01 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >> I see this report is from 16th June 2021 and the commit is on 18th
> >> June 2021. So, I am hoping this should have been fixed but if we see
> >> it again then probably we need to investigate it further.
>
> > Ahh, that makes sense.  Thanks for checking, and sorry for the noise.
>
> 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.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Greg Nancarrow
Date:
Subject: Re: Parallel scan with SubTransGetTopmostTransaction assert coredump
Next
From: Amit Kapila
Date:
Subject: Re: Optionally automatically disable logical replication subscriptions on error