From: Ronan Dunklau <ronan.dunklau@aiven.io>
To: Masahiko Sawada <sawada.mshk@gmail.com>, pgsql-bugs@lists.postgresql.org
Cc: "Gerard H. Pille" <ghpille@hotmail.com>,
 PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>,
 Michael Paquier <michael@paquier.xyz>
Subject: Re: pg_basebackup behavior on non-existent slot
Date: Thu, 26 Aug 2021 07:31:31 +0200
Message-ID: <1795827.0SXAIGXuGy@aivenronan>
Organization: aiven
In-Reply-To: <YSNKEJFmA+amz515@paquier.xyz>
References: 
 <PA4PR04MB78886C76F521F031FDEB216CBCC29@PA4PR04MB7888.eurprd04.prod.outlook.com>
 <CAD21AoA=D1ssWr-GOPz-NMr4jDsZb2VGetdRVvXeQXtdiLoBUA@mail.gmail.com>
 <YSNKEJFmA+amz515@paquier.xyz>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Archived-At: 
 <https://www.postgresql.org/message-id/1795827.0SXAIGXuGy%40aivenronan>
Precedence: bulk

Le lundi 23 ao=FBt 2021, 09:11:12 CEST Michael Paquier a =E9crit :
Some ideas here
> may be to extend the result of IDENTIFY_SYSTEM to return the slots
> available in a text array, invent a new command called SLOT, use SHOW
> or perhaps do an extra CREATE_REPLICATION_SLOT TEMPORARY from the main
> thread.

This new command (albeit named differently, READ_REPLICATION_SLOT) has been=
=20
proposed here: https://www.postgresql.org/message-id/
1642037.dBafQRxpgh@aivenronan for a different purpose, although it would be=
=20
useful to have that in that case too.

I guess I can add a patch to use that in pg_basebackup itself in the same=20
patchset.

=2D-=20
Ronan Dunklau