Postgres Pro
Downloads
Home   >   mailing lists

pg_stat_replication log positions vs base backups - Mailing list pgsql-hackers

From Magnus Hagander
Subject pg_stat_replication log positions vs base backups
Date
Msg-id CABUevEzyXPpnMhQPugZr68sFL5UC_3t+=WY4uBm8Z5nEuoT5UA@mail.gmail.com
Whole thread Raw
Responses Re: pg_stat_replication log positions vs base backups  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Tree view
Are the values for the log locations really relevant for backup connections? And if they are, we need to document it :) ISTM we are just more or less leaking random data out there?

I'm talking about the actual state=backup connection - not the connection if we're using -x with pg_basebackup. Where we have output like:

state            | backup
sent_location    | 0/0
write_location   | 2/76CE0000
flush_location   | 2/76CC0000
replay_location  | 2/76CBF938

I'm thinking those fields should probably all be NULL for state=backup?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: pg_hba_lookup function to get all matching pg_hba.conf entries
Next
From: YUriy Zhuravlev
Date:
Subject: Re: WIP: About CMake v2