Re: pg_basebackup behavior on non-existent slot

From: Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: "Gerard H(dot) Pille" <ghpille(at)hotmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: pg_basebackup behavior on non-existent slot
Date: 2021-08-26 05:31:31
Message-ID: 1795827.0SXAIGXuGy@aivenronan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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(dot)dBafQRxpgh(at)aivenronan for a different purpose, although it would be
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
patchset.

--
Ronan Dunklau

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Anupam Pandey 2021-08-26 05:54:49 Issue/Abnormality found.
Previous Message PG Bug reporting form 2021-08-26 05:07:48 BUG #17162: order by clause is not pushed down to foreign scans when a WHERE clause is given in query