Re: [HACKERS] IF [NOT] EXISTS for replication slots
От | Petr Jelinek |
---|---|
Тема | Re: [HACKERS] IF [NOT] EXISTS for replication slots |
Дата | |
Msg-id | 65f2f415-54b1-3e9d-1eea-ccbc693c9766@2ndquadrant.com обсуждение исходный текст |
Ответ на | [HACKERS] IF [NOT] EXISTS for replication slots (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] IF [NOT] EXISTS for replication slots
|
Список | pgsql-hackers |
On 06/02/17 05:15, Michael Paquier wrote: > 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? > My thought is, how would this handle the snapshot creation that logical slot does when it's created? -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: