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>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Function to get invalidation cause of a replication slot.
Date: 2023-12-20 11:43:45
Message-ID: 18431286-04fe-4e8a-802f-5910102fe2dd@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 12/20/23 10:55 AM, shveta malik wrote:
> On Wed, Dec 20, 2023 at 2:20 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
>
> PFA v2 patch. Addressed below comments:
>
> 1) Added test in 019_replslot_limit.pl
> 2) 'pg_get_slot_invalidation_cause' now returns error if the given
> slot does not exist
> 3) Corrected doc and commit msg.

Thanks!

+ <literal>3</literal> = wal_level insufficient on the primary server

"." is missing at the end (to be consistent with 1 and 2). Same
in the commit message.

+ * Returns ReplicationSlotInvalidationCause enum value for valid slot_name;

Not sure the sentence should finish with ";".

Another Nit is to add a comment in ReplicationSlotInvalidationCause definition (slot.h)
that any new enum values (if any) should be added after the ones that are already defined (to
provide some consistency across changes in this area if any).

Except the above Nit(s) the patch LGTM.

Regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-12-20 11:49:27 ci: Build standalone INSTALL file
Previous Message Andres Freund 2023-12-20 11:40:27 Re: Remove MSVC scripts from the tree