From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | "S(dot) Bob" <sbob(at)quadratum-braccas(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: xmin value from pg_stat_replication |
Date: | 2019-07-17 18:38:08 |
Message-ID: | 87a7dc8q27.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"S. Bob" <sbob(at)quadratum-braccas(dot)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(dot)consulting(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-07-17 20:32:04 | Re: xmin value from pg_stat_replication |
Previous Message | S. Bob | 2019-07-17 18:31:29 | xmin value from pg_stat_replication |