From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Owen Stephens <owen@owenstephens.co.uk>
To: pgsql-general@lists.postgresql.org
Subject: Re: Unexpected cross-database vacuum impact with hot_standby_feedback=on
Date: Fri, 19 May 2023 22:50:16 +0200
Message-ID: <8f1be0222b943a6fc99e7ef6283bd144d2d3447a.camel@cybertec.at> (raw)
In-Reply-To: <CANOh7gGqY39TnTb-WBvrSVpY0UXNXv-eoXYqdkSV6acHUx272Q@mail.gmail.com>
References: <CANOh7gGqY39TnTb-WBvrSVpY0UXNXv-eoXYqdkSV6acHUx272Q@mail.gmail.com>
On Thu, 2023-05-18 at 17:34 +0100, Owen Stephens wrote:
> We are seeing that vacuum is prevented from cleaning dead tuples by an open
> transaction in a different database (where both connections are made against the
> primary server) when hot_standby_feedback = on but not when it is off. Is this
> cross-database interaction an expected effect of enabling hot_standby_feedback,
> even if the connections interact only with the primary not the replica?
Yes, that's what I would expect. There is only one "backend_xmin" in
"pg_stat_replication", which corresponds to the snapshot held by the oldest
query in any database on the standby server.
Yours,
Laurenz Albe
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: laurenz.albe@cybertec.at, owen@owenstephens.co.uk
Subject: Re: Unexpected cross-database vacuum impact with hot_standby_feedback=on
In-Reply-To: <8f1be0222b943a6fc99e7ef6283bd144d2d3447a.camel@cybertec.at>
References: <CANOh7gGqY39TnTb-WBvrSVpY0UXNXv-eoXYqdkSV6acHUx272Q@mail.gmail.com> <8f1be0222b943a6fc99e7ef6283bd144d2d3447a.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox