Re: Unexpected cross-database vacuum impact with hot_standby_feedback=on

2023-05-22 Thread Owen Stephens
On Fri, May 19, 2023 at 9:50 PM Laurenz Albe wrote: > 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. > Thanks for the pointer to

Unexpected cross-database vacuum impact with hot_standby_feedback=on

2023-05-19 Thread Owen Stephens
Hi, 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