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 pg_stat_replication
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 i
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
rpin,
> > > confl_deadlock
> > > FROM pg_stat_database_conflicts
> > > WHERE datname = 'something' \gx
> > >
> > > -[ RECORD 1 ]+--
> > > confl_tablespace | 0
> > > confl_lock | 0
> > > confl_snapshot | 84990
> &g
me = 'something' \gx
> >
> > -[ RECORD 1 ]+--
> > confl_tablespace | 0
> > confl_lock | 0
> > confl_snapshot | 84990
> > confl_bufferpin | 0
> > confl_deadlock | 0
> >
> > SHOW hot_standby_feedback;
> >
&g
;something' \gx
>
> -[ RECORD 1 ]+--
> confl_tablespace | 0
> confl_lock | 0
> confl_snapshot | 84990
> confl_bufferpin | 0
> confl_deadlock | 0
>
> SHOW hot_standby_feedback;
>
> hot_standby_feedback
> --
> on
> (1 row)
>
>
pshot | 84990
confl_bufferpin | 0
confl_deadlock | 0
SHOW hot_standby_feedback;
hot_standby_feedback
------
on
(1 row)
This is PostgreSQL 11.7, the standby didn't disconnect from the primary, and
the number of replication conflicts is growing.
I had thought that "hot_sta
Dear, I have a query to make you
As much as you enable hot_standby_feedback = on, queries continue to be
canceled, in addition to enabling this parameter you have to modify any of
these?
#max_standby_archive_delay = 30s
#max_standby_streaming_delay = 30s
#wal_receiver_status_interval = 10s
The
Hello,
Can I skip function ResolveRecoveryConflictWithSnapshot if setting
hot_standby_feedback=on all the time?
As I know, function ResolveRecoveryConflictWithSnapshot is used for resolving
conflicts once master cleans dead tuples. But if I set hot_standby_feedback to
on, it will not appear
