[HACKERS] IF [NOT] EXISTS for replication slots - Mailing list pgsql-hackers

From Michael Paquier
Subject [HACKERS] IF [NOT] EXISTS for replication slots
Date
Msg-id CAB7nPqR__V5HoDfHiWhSGmNjaicGawokhVA6Ka6S+HmEymo=7Q@mail.gmail.com
Whole thread Raw
Responses Re: [HACKERS] IF [NOT] EXISTS for replication slots  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
Hi all,

Lately I have bumped into a case where it would have been useful to
make the difference between a failure because of a slot already
dropped and an internal failure of Postgres. Is there any interest for
support of IE and INE for CREATE and DROP_REPLICATION_SLOT?
My use case involved only the SQL-callable interface, but I would
think that it is useful to make this difference as well with the
replication protocol. For the function we could just add a boolean
argument to control the switch, and for the replication commands a
dedicated keyword.

Any thoughts?
-- 
Michael



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY
Next
From: Pavan Deolasee
Date:
Subject: Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY