Subject: Re: pg_xlog piling
To: Jorge Torralba <jorge.torralba@gmail.com>,
 "David G. Johnston" <david.g.johnston@gmail.com>
Cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
References: <575c1026-aabd-4854-55f7-1292c57b3da6@pgsqlrocket.com>
 <CAKFQuwa1-KWVC=jjX4GoGS0VposoO0Y-gVugC0fH60YiwcNF1g@mail.gmail.com>
 <CACut7uR2MGJDWWrAcHPjNsK-UvPKmNUi-166vEXO0HwA7=F2aA@mail.gmail.com>
From: chris <chrisk@pgsqlrocket.com>
Message-ID: <5ea7febf-4697-ff4d-4ee4-aa9508feb6e1@pgsqlrocket.com>
Date: Tue, 30 Jan 2018 14:31:59 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: 
 <CACut7uR2MGJDWWrAcHPjNsK-UvPKmNUi-166vEXO0HwA7=F2aA@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------E9F24E1C0B1BFC4D30B2D06F"
Content-Language: en-US
Precedence: bulk

This is a multi-part message in MIME format.
--------------E9F24E1C0B1BFC4D30B2D06F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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.


--------------E9F24E1C0B1BFC4D30B2D06F
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <pre wrap="">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=# 


</pre>
    # - Archiving -<br>
    <br>
    archive_mode = on        # allows archiving to be done<br>
    <br>
    archive_command = 'cp %p /ComplianceDB/pitr/walstage/%f; mv
    /ComplianceDB/pitr/walstage/%f /ComplianceDB/pitr/wal/%f'           
        # (change requires restart)<br>
    #archive_command = ''        # command to use to archive a logfile
    segment<br>
                    # placeholders: %p = path of file to archive<br>
                    #               %f = file name only<br>
                    # e.g. 'test ! -f /mnt/server/archivedir/%f
    &amp;&amp; cp %p /mnt/server/archivedir/%f'<br>
    #archive_timeout = 0        # force a logfile segment switch after
    this<br>
                    # number of seconds; 0 disables<br>
    Thanks<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 01/30/2018 12:59 PM, Jorge Torralba
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CACut7uR2MGJDWWrAcHPjNsK-UvPKmNUi-166vEXO0HwA7=F2aA@mail.gmail.com">
      <div dir="ltr">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 ?</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Tue, Jan 30, 2018 at 11:09 AM, David
          G. Johnston <span dir="ltr">&lt;<a
              href="mailto:david.g.johnston@gmail.com" target="_blank"
              moz-do-not-send="true">david.g.johnston@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><span
              class="">On Tuesday, January 30, 2018, chris &lt;<a
                href="mailto:chrisk@pgsqlrocket.com" target="_blank"
                moz-do-not-send="true">chrisk@pgsqlrocket.com</a>&gt;
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">This
                was a problem before when we were on postgresl 9.2 <br>
              </blockquote>
              <div><br>
              </div>
            </span>
            <div>What version are you on now?</div>
            <div><br>
            </div>
            <div>David J. </div>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        <div class="gmail_signature" data-smartmail="gmail_signature">Thanks,<br>
          <br>
          Jorge Torralba<br>
          ----------------------------<br>
          <br>
          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.</div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------E9F24E1C0B1BFC4D30B2D06F--