Re: Track in pg_replication_slots the reason why slots conflict?

Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: Amit Kapila <amit.kapila16@gmail.com>, Andres Freund <andres@anarazel.de>, shveta malik <shveta.malik@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>

Date: 2023-12-26T08:50:00Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Track conflict_reason in pg_replication_slots.
- 007693f2a3ac 17.0 landed

Hi,

On Tue, Dec 26, 2023 at 05:23:56PM +0900, Michael Paquier wrote:
> On Tue, Dec 26, 2023 at 08:44:44AM +0530, Amit Kapila wrote:
> > Does anyone else have a preference on whether to change the existing
> > column or add a new one?
> 
> Just to be clear here, I'd vote for replacing the existing boolean
> with a text.

Same here, I'd vote to avoid 2 columns having the same "meaning".

Regards,

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