From: Jerry Sievers <gsievers19@comcast.net>
To: S. Bob <sbob@quadratum-braccas.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: xmin value from pg_stat_replication
Date: Wed, 17 Jul 2019 13:38:08 -0500
Message-ID: <87a7dc8q27.fsf@jsievers.enova.com> (raw)
In-Reply-To: <2bbb14f7-b894-cf98-986f-59e4711d0aa5@quadratum-braccas.com>
References: <2bbb14f7-b894-cf98-986f-59e4711d0aa5@quadratum-braccas.com>
"S. Bob" <sbob@quadratum-braccas.com> writes:
> All;
>
>
> We have a master and a standby (Streaming replication).
>
> This query produces a value of approx 1.5million on the master and
> approx 80million on the standby:
>
>
> select slot_name, slot_type, database, xmin from pg_replication_slots
> order by age(xmin);
Why does your standby have rep slots? Is it also feeding lower
subordinate standbys?
>
>
> We are running replication in async mode.
>
>
> A couple of questions:
>
>
> - Is it unusual for the master & standby to differ dramatically like this?
>
> - could the replication slot (i.e. the xmin on the standby) be
> preventing vacuum from cleaning up row versions on the master?
>
>
> Thanks in advance
>
>
>
>
>
>
>
>
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
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: pgsql-admin@postgresql.org
Cc: gsievers19@comcast.net, sbob@quadratum-braccas.com, pgsql-admin@lists.postgresql.org
Subject: Re: xmin value from pg_stat_replication
In-Reply-To: <87a7dc8q27.fsf@jsievers.enova.com>
* 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