From: chris <chrisk@pgsqlrocket.com>
To: Jorge Torralba <jorge.torralba@gmail.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: pg_xlog piling
Date: Tue, 30 Jan 2018 14:31:59 -0700
Message-ID: <5ea7febf-4697-ff4d-4ee4-aa9508feb6e1@pgsqlrocket.com> (raw)
In-Reply-To: <CACut7uR2MGJDWWrAcHPjNsK-UvPKmNUi-166vEXO0HwA7=F2aA@mail.gmail.com>
References: <575c1026-aabd-4854-55f7-1292c57b3da6@pgsqlrocket.com>
<CAKFQuwa1-KWVC=jjX4GoGS0VposoO0Y-gVugC0fH60YiwcNF1g@mail.gmail.com>
<CACut7uR2MGJDWWrAcHPjNsK-UvPKmNUi-166vEXO0HwA7=F2aA@mail.gmail.com>
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.g.johnston@gmail.com <mailto:david.g.johnston@gmail.com>> wrote:
>
> On Tuesday, January 30, 2018, chris <chrisk@pgsqlrocket.com
> <mailto:chrisk@pgsqlrocket.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: chrisk@pgsqlrocket.com, jorge.torralba@gmail.com, david.g.johnston@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_xlog piling
In-Reply-To: <5ea7febf-4697-ff4d-4ee4-aa9508feb6e1@pgsqlrocket.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox