public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alvaro Herrera <[email protected]>
To: Antonin Houska <[email protected]>
Cc: Srinath Reddy Sadipiralla <[email protected]>
Cc: Amit Kapila <[email protected]>
Cc: Mihail Nikalayeu <[email protected]>
Cc: Matthias van de Meent <[email protected]>
Cc: Pg Hackers <[email protected]>
Cc: Robert Treat <[email protected]>
Subject: Re: Adding REPACK [concurrently]
Date: Fri, 3 Apr 2026 19:24:30 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <90475.1775218118@localhost>
On 2026-Apr-03, Antonin Houska wrote:
> diff --git a/src/backend/commands/repack_worker.c b/src/backend/commands/repack_worker.c
> index 00b21ede481..c25dbeadff3 100644
> --- a/src/backend/commands/repack_worker.c
> +++ b/src/backend/commands/repack_worker.c
> @@ -233,6 +234,13 @@ repack_setup_logical_decoding(Oid relid)
>
> EnsureLogicalDecodingEnabled();
>
> + /*
> + * By declaring that our output plugin does not need shared catalogs, we
> + * avoid waiting for completion of transactions running in other databases
> + * than the one we're connected to.
> + */
> + accessSharedCatalogsInDecoding = false;
> +
> /*
> * Neither prepare_write nor do_write callback nor update_progress is
> * useful for us.
I find this reliance on a global variable for this a bit icky. Would it
work to instead change the CreateInitDecodingContext() signature, so
that instead of "bool need_full_snapshot" it has a three-valued boolean
to distinguish the two cases from the original plus this new one? I
think the value could be stored in LogicalDecodingContext, from where
standby_decode() could obtain it.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"The important things in the world are problems with society that we don't
understand at all. The machines will become more complicated but they won't
be more complicated than the societies that run them." (Freeman Dyson)
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], [email protected], [email protected], [email protected]
Subject: Re: Adding REPACK [concurrently]
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