public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: Amit Kapila <[email protected]>
Cc: Postgres hackers <[email protected]>
Cc: Bertrand Drouvot <[email protected]>
Cc: Andres Freund <[email protected]>
Subject: Re: Track in pg_replication_slots the reason why slots conflict?
Date: Thu, 21 Dec 2023 12:07:56 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAA4eK1+Rp2gODDaWEOdpprVFUgj7P9xtsZT+SSsOT_oWPxUqDQ@mail.gmail.com>
References: <[email protected]>
<CAA4eK1+Rp2gODDaWEOdpprVFUgj7P9xtsZT+SSsOT_oWPxUqDQ@mail.gmail.com>
On Thu, Dec 21, 2023 at 08:20:16AM +0530, Amit Kapila wrote:
> The invalidation cause is also required by one of the features being
> discussed "Synchronize slots from primary to standby" [1] and there is
> already a thread to discuss the same [2]. As that thread started
> yesterday only, you may not have noticed it. Currently, the proposal
> is to expose it via a function but we can extend it to also display
> via view, feel free to share your opinion on that thread.
>
> [1] - https://www.postgresql.org/message-id/[email protected]
> [2] - https://www.postgresql.org/message-id/CAJpy0uBpr0ym12%2B0mXpjcRFA6N%3DanX%2BYk9aGU4EJhHNu%3DfWykQ%40...
Ah thanks, missed this one. This cannot use a separate function,
actually, and there is a good reason for that that has not been
mentioned. I'll jump there.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, ../[email protected]/2-signature.asc)
download
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Track in pg_replication_slots the reason why slots conflict?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox