Re: Track in pg_replication_slots the reason why slots conflict?

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Subject: Re: Track in pg_replication_slots the reason why slots conflict?
Date: 2024-01-02 05:05:59
Message-ID: CAA4eK1+3CDHGXyaQhBdj0X=hyDtZWOSrm+X6dsHsLOt+0Dt-cQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 1, 2024 at 5:24 PM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
> Please ignore the previous patch and PFA new v4 (v4_2). The only
> change from the earlier v4 is the subject correction in commit msg.
>

The patch looks good to me. I have slightly changed one of the
descriptions in the docs and also modified the commit message a bit. I
will push this after two days unless there are any more
comments/suggestions.

--
With Regards,
Amit Kapila.

Attachment Content-Type Size
v5-0001-Track-conflict_reason-in-pg_replication_slots.patch application/octet-stream 13.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhang Mingli 2024-01-02 05:12:22 Re: Minor cleanup for search path cache
Previous Message Alexander Lakhin 2024-01-02 05:00:00 Re: Random pg_upgrade test failure on drongo