BUG #14036: xmin is null in pg_relication_slots
The following bug has been logged on the website:
Bug reference: 14036
Logged by: Jamie Koceniak
Email address: jkoceniak@mediamath.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 |
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On March 19, 2016 12:24:16 PM PDT, jkoceniak@mediamath.com wrote:
The following bug has been logged on the website:
Bug reference: 14036
Logged by: Jamie Koceniak
Email address: jkoceniak@mediamath.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.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs