Re: pg_basebackup behavior on non-existent slot - Mailing list pgsql-bugs

From Masahiko Sawada
Subject Re: pg_basebackup behavior on non-existent slot
Date
Msg-id CAD21AoDYmv0yJMQnWtCx_kZGwVZnkQSTQ1re2JNSgM0k37afYQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_basebackup behavior on non-existent slot  (Ronan Dunklau <ronan.dunklau@aiven.io>)
Responses Re: pg_basebackup behavior on non-existent slot  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
On Thu, Aug 26, 2021 at 2:31 PM Ronan Dunklau <ronan.dunklau@aiven.io> wrote:
>
> Le lundi 23 août 2021, 09:11:12 CEST Michael Paquier a écrit :
> 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
> proposed here: https://www.postgresql.org/message-id/
> 1642037.dBafQRxpgh@aivenronan for a different purpose, although it would be
> useful to have that in that case too.

Cool! I was considering other use cases of those new command ideas
proposed on this thread.

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

+1

I'll look at the patches.

Regards,

--
Masahiko Sawada
EDB:  https://www.enterprisedb.com/



pgsql-bugs by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: BUG #17157: authorizaiton of dict_int and bloom extention
Next
From: constzl
Date:
Subject: Is Backgroundworker.bgw_restart_time is defined in seconds?