IF [NOT] EXISTS for replication slots

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: IF [NOT] EXISTS for replication slots
Date: 2017-02-06 04:15:15
Message-ID: CAB7nPqR__V5HoDfHiWhSGmNjaicGawokhVA6Ka6S+HmEymo=7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2017-02-06 04:17:43 Re: Index corruption with CREATE INDEX CONCURRENTLY
Previous Message Amit Kapila 2017-02-06 04:11:00 Re: Index corruption with CREATE INDEX CONCURRENTLY