Re: pg_xlog piling

postgres=# select * from pg_stat_replication;
pid | usesysid | usename | application_name | client_addr |
client_hostname | client_port | backend_start | state |
sent_location | write_location | flush_location | replay_locatio
n | sync_priority | sync_state
------+----------+----------+------------------+----------------+-----------------+-------------+-------------------------------+-----------+---------------+----------------+----------------+---------------
--+---------------+------------
5303 | 10 | postgres | walreceiver | 198.161.184.74 |
| 57049 | 2017-12-14 11:13:16.339948-07 | streaming | 2FD3/41A38140 |
2FD3/41A38140 | 2FD3/41A38140 | 2F47/7015D490
| 0 | async
(1 row)

postgres=#

# - Archiving -

archive_mode = on        # allows archiving to be done

archive_command = 'cp %p /ComplianceDB/pitr/walstage/%f; mv
/ComplianceDB/pitr/walstage/%f /ComplianceDB/pitr/wal/%f'     # (change
requires restart)
#archive_command = ''        # command to use to archive a logfile segment
                # placeholders: %p = path of file to archive
                #               %f = file name only
                # e.g. 'test ! -f /mnt/server/archivedir/%f && cp %p
/mnt/server/archivedir/%f'
#archive_timeout = 0        # force a logfile segment switch after this
                # number of seconds; 0 disables
Thanks

On 01/30/2018 12:59 PM, Jorge Torralba wrote:
> what is your archive command and is your replica up to date?  Any
> messages in the pg_log that would indicate the replica is not
> receiving update ?
>
> On Tue, Jan 30, 2018 at 11:09 AM, David G. Johnston
> <david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>> wrote:
>
> On Tuesday, January 30, 2018, chris <chrisk(at)pgsqlrocket(dot)com
> <mailto:chrisk(at)pgsqlrocket(dot)com>> wrote:
>
> This was a problem before when we were on postgresl 9.2
>
>
> What version are you on now?
>
> David J.
>
>
>
>
> --
> Thanks,
>
> Jorge Torralba
> ----------------------------
>
> Note: This communication may contain privileged or other confidential
> information. If you are not the intended recipient, please do not
> print, copy, retransmit, disseminate or otherwise use the information.
> Please indicate to the sender that you have received this email in
> error and delete the copy you received. Thank You.