Re: Function to get invalidation cause of a replication slot.

From: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: Function to get invalidation cause of a replication slot.
Date: 2023-12-20 10:44:49
Message-ID: 2889ac8f-1388-4bdf-b5b3-0712a5d1f1c1@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 12/20/23 10:57 AM, shveta malik wrote:
> On Wed, Dec 20, 2023 at 12:46 PM Drouvot, Bertrand
>> Worth to add some coverage in 019_replslot_limit.pl and 035_standby_logical_decoding.pl?
>
> I have recently added a test in 019_replslot_limit.pl in v2.

Thanks!

> Do you
> suggest adding in 035_standby_logical_decoding as well? Will it have
> additional benefits?

That would cover the remaining invalidation causes but I'm not sure
that's worth it as this new function is simple enough after all.

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2023-12-20 10:45:55 Re: Remove MSVC scripts from the tree
Previous Message Drouvot, Bertrand 2023-12-20 10:40:03 Re: Function to get invalidation cause of a replication slot.