Re: xmin value from pg_stat_replication - Mailing list pgsql-admin

From Jerry Sievers
Subject Re: xmin value from pg_stat_replication
Date
Msg-id 87a7dc8q27.fsf@jsievers.enova.com
Whole thread Raw
In response to xmin value from pg_stat_replication  ("S. Bob" <sbob@quadratum-braccas.com>)
List pgsql-admin
"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



pgsql-admin by date:

Previous
From: "S. Bob"
Date:
Subject: xmin value from pg_stat_replication
Next
From: Andres Freund
Date:
Subject: Re: xmin value from pg_stat_replication