Re: pg_basebackup and replication slots
От | Simon Riggs |
---|---|
Тема | Re: pg_basebackup and replication slots |
Дата | |
Msg-id | CANP8+jK2UWejgZPspu=XWvA1=Yj0JqJ3uKvXaC9gdr=EXanpRw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_basebackup and replication slots (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: pg_basebackup and replication slots
|
Список | pgsql-hackers |
On 22 July 2015 at 05:43, Michael Paquier <michael.paquier@gmail.com> wrote:
--
Now, do we plan to do something about the creation of a slot. I
imagine that it would be useful if we could have --create-slot to
create a slot when beginning a base backup and if-not-exists to
control the error flow. There is already CreateReplicationSlot for
this purpose in streamutils.c so most of the work is already done.
Also, when a base backup fails for a reason or another, we should try
to drop the slot in disconnect_and_exit() if it has been created by
pg_basebackup. if if-not-exists is true and the slot already existed
when beginning, we had better not dropping it perhaps...
What is the purpose of creating a temporary slot?
My understand was that slots are supposed to be persistent so we should create them before use.
If we create a slot when one is needed and then drop automatically on session disconnect (as Heikki suggest), what benefit does using a slot give us?
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: