From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: behave of --create-slot option |
Date: | 2018-05-29 01:28:25 |
Message-ID: | CAMsr+YFPE2yaunpD4PNiw0=vm8enXet-cL23Xc7ZubJbTTQpyw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 29 May 2018 at 03:41, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> Hi
>
> I am writing a article about PostgreSQL 11 features. Now I am looking on
> new option --create-slot option of pg_basebackup command.
>
> I don't understand to use case for this option, because It fails when
> requested slot already exists. I cannot to imagine use case for this. If I
> write some scripts, then I prefer the behave like "create if doesn't exist
> or do nothing".
>
> Any repeated running of script with this option should to fail. Is it
> required? Why?
>
>
The slot is intended to then be used by a replica that was created by
pg_basebackup. I think it writes the slot name into recovery.conf; if it
doesn't, it should.
So you use a unique slot name for each replica.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Yuriy Zhuravlev | 2018-05-29 01:59:47 | Re: Is a modern build system acceptable for older platforms |
Previous Message | Euler Taveira | 2018-05-29 00:11:50 | Re: behave of --create-slot option |