Re: BUG #14036: xmin is null in pg_relication_slots

From: Andres Freund <andres(at)anarazel(dot)de>
To: jkoceniak(at)mediamath(dot)com,pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14036: xmin is null in pg_relication_slots
Date: 2016-03-19 22:17:07
Message-ID: 99927514-B1E1-4CE7-915D-3F57180C2FAC@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On March 19, 2016 12:24:16 PM PDT, jkoceniak(at)mediamath(dot)com wrote:
>The following bug has been logged on the website:
>
>Bug reference: 14036
>Logged by: Jamie Koceniak
>Email address: jkoceniak(at)mediamath(dot)com
>PostgreSQL version: 9.4.6
>Operating system: Debian
>Description:
>
>We just configured 6 replication slots and I noticed that 2 of the 6
>replication slots have a NULL value for xmin. Is this problematic?
>
>postgres=# select slot_name, xmin from pg_replication_slots;
> slot_name | xmin
>----------------+------------
> standb5 | 1571582845
> standby3 | 1571582849
> standby6 | 1571582850
> standby4 | 1571582853
> standby2 |
> standby1 |

Have you enabled hot_standby_feedback on those? Are act queries running on them?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2016-03-19 22:38:26 Re: BUG #14033: cross-compilation to ARM fails
Previous Message jkoceniak 2016-03-19 19:24:16 BUG #14036: xmin is null in pg_relication_slots