From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup and replication slots |
Date: | 2015-07-29 07:57:38 |
Message-ID: | CANP8+jK2UWejgZPspu=XWvA1=Yj0JqJ3uKvXaC9gdr=EXanpRw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 22 July 2015 at 05:43, Michael Paquier <michael(dot)paquier(at)gmail(dot)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/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-07-29 07:58:51 | Re: Don'st start streaming after creating a slot in pg_receivexlog |
Previous Message | Simon Riggs | 2015-07-29 07:54:40 | Re: Don'st start streaming after creating a slot in pg_receivexlog |