Re: Diagnostic comment in LogicalIncreaseXminForSlot

From: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Diagnostic comment in LogicalIncreaseXminForSlot
Date: 2021-05-21 09:00:00
Message-ID: CAGEoWWQfV6mJS336c=219+mP5oJUm9ML9zSE4EStstRhvcbAog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 21, 2021 at 11:26 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:

> On Thu, May 20, 2021 at 5:43 PM Ashutosh Bapat
> <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> wrote:
> >
> > Hi
> > LogicalIncreaseRestartDecodingForSlot() has a debug log to report a
> > new restart_lsn. But the corresponding function for catalog_xmin.
> > Here's a patch to add the same.
> >
>
> I think this can be useful. One minor comment:
> + elog(DEBUG1, "got new catalog_xmin %u at %X/%X", xmin,
> + (uint32) (current_lsn >> 32), (uint32) current_lsn);
>
> Isn't it better to use LSN_FORMAT_ARGS for current_lsn?

Thanks for reminding me about that. :).

Attached revised patch.

> Also, there
> doesn't seem to be any urgency for adding this, so you can register it
> for the next CF so that we can add this when the branch opens for
> PG-15.
>

It's there in CF. I am fine with PG-15. It will be good to patch the
back-branches to have this extra diagnostic information available.

--
Best Wishes,
Ashutosh

Attachment Content-Type Size
0001-Report-new-catalog_xmin-candidate-in-LogicalIncrease.patch text/x-patch 1.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2021-05-21 09:03:17 Re: Fdw batch insert error out when set batch_size > 65535
Previous Message Laurenz Albe 2021-05-21 08:52:42 Re: Additional Chapter for Tutorial