Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42619=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1X5f3d-0006BC-2L
 for pgsql-admin@arkaria.postgresql.org; Fri, 11 Jul 2014 17:56:29 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M42619=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1X5f3c-0006IA-0m
 for pgsql-admin@arkaria.postgresql.org; Fri, 11 Jul 2014 17:56:28 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1X5f3b-0006I3-3O
 for pgsql-admin@postgresql.org; Fri, 11 Jul 2014 17:56:27 +0000
Received: from mail-yk0-x22a.google.com ([2607:f8b0:4002:c07::22a])
 by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1X5f3X-0005AE-UK
 for pgsql-admin@postgresql.org; Fri, 11 Jul 2014 17:56:25 +0000
Received: by mail-yk0-f170.google.com with SMTP id q9so548773ykb.1
 for <pgsql-admin@postgresql.org>; Fri, 11 Jul 2014 10:56:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type;
 bh=sZT9uvPi9hx4C4A4L3gJ548FwVA86tmc27Q9qQmGUF0=;
 b=urz1nsCrCuQI0P4XrTytHBDaV/t48yD0mUnQQIPOCRoCbol15RrYT/9ocPe97pOY3A
 acfR92UkucPH49g+8DB/TeOpLiHTBwgeqkdZxC5/4e9anNJkWdn+hIa5eO5kBDPrSTx2
 4695HWKLve7m1jnI4mDxYsztjJS1sJiRO8xfK6Xfle9aAdvWLMs/FUfK+SZrm/Z6lP9n
 zooIcND0c2Jv1jkWvEkle8EGGI4wkHXnZ7SBzTyuHyhaAW23hWSg24vdxq7pna+2OcpO
 ob2TnDa7+3idFtIi7o9DZnI0QeU3i3mIPIMFNORbtUP/n0Qn57Qv/az1XKklnLnt74l1
 7NGg==
X-Received: by 10.236.142.242 with SMTP id i78mr505204yhj.17.1405101383029;
 Fri, 11 Jul 2014 10:56:23 -0700 (PDT)
Received: from [192.168.254.5] (h77.89.102.166.static.ip.windstream.net.
 [166.102.89.77])
 by mx.google.com with ESMTPSA id g68sm6352113yhf.52.2014.07.11.10.56.22
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Fri, 11 Jul 2014 10:56:22 -0700 (PDT)
Message-ID: <53C02540.4000107@gmail.com>
Date: Fri, 11 Jul 2014 13:56:16 -0400
From: John Scalia <jayknowsunix@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Matheus de Oliveira <matioli.matheus@gmail.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: WAL segment management on a standby
References: <53C015AA.5070908@gmail.com>
 <CAJghg4LwTAGDHhFA-=dNHM8_HxDhybyr1LiST7+hFu7xdo=E8w@mail.gmail.com>
In-Reply-To: 
 <CAJghg4LwTAGDHhFA-=dNHM8_HxDhybyr1LiST7+hFu7xdo=E8w@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------040907030909050104090405"
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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

Thanks Matheus,

What I guess I'm more than curious about is as this is one of two standbys and I could always rebuild it again from either of the other two machines, is what am I risking if delete 
everything except maybe the last handful of WAL segments? When I start the database, I usually only see one or maybe two references to WAL segments being used to sync up. And being 
that the standby streams anyway, I'm not all that concerned if another pg_basebackup has to run to rebuild the standby. I only want it to start cleanly in the event of a stoppage. 
Which almost never happens anyway.
--
Jay

On 7/11/2014 12:58 PM, Matheus de Oliveira wrote:
>
> On Fri, Jul 11, 2014 at 1:49 PM, John Scalia <jayknowsunix@gmail.com <mailto:jayknowsunix@gmail.com>> wrote:
>
>     00000000300000000C000000A1
>     00000000300000000C000000A2
>     00000000300000000C000000A3
>     00000000300000000C000000A3.backup
>     00000000300000000C000000A4
>
>     Could I safely delete the *A1, *A2, and maybe even the *A3 files?
>
>
> If you only care to storing files needed for backup made at 00000000300000000C000000A3, you can remove 00000000300000000C000000A1 and 00000000300000000C000000A2, but not the others.
>
> Regards,
> -- 
> Matheus de Oliveira
> Analista de Banco de Dados
> Dextra Sistemas - MPS.Br nível F!
> www.dextra.com.br/postgres <http://www.dextra.com.br/postgres/>
>


--------------040907030909050104090405
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Thanks Matheus,<br>
    <br>
    What I guess I'm more than curious about is as this is one of two
    standbys and I could always rebuild it again from either of the
    other two machines, is what am I risking if delete everything except
    maybe the last handful of WAL segments? When I start the database, I
    usually only see one or maybe two references to WAL segments being
    used to sync up. And being that the standby streams anyway, I'm not
    all that concerned if another pg_basebackup has to run to rebuild
    the standby. I only want it to start cleanly in the event of a
    stoppage. Which almost never happens anyway.<br>
    --<br>
    Jay<br>
    <br>
    <div class="moz-cite-prefix">On 7/11/2014 12:58 PM, Matheus de
      Oliveira wrote:<br>
    </div>
    <blockquote
cite="mid:CAJghg4LwTAGDHhFA-=dNHM8_HxDhybyr1LiST7+hFu7xdo=E8w@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Fri, Jul 11, 2014 at 1:49 PM, John
            Scalia <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:jayknowsunix@gmail.com" target="_blank">jayknowsunix@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div id=":12q" class="" style="overflow:hidden">
                00000000300000000C000000A1<br>
                00000000300000000C000000A2<br>
                00000000300000000C000000A3<br>
                00000000300000000C000000A3.backup<br>
                00000000300000000C000000A4<br>
                <br>
                Could I safely delete the *A1, *A2, and maybe even the
                *A3 files?</div>
            </blockquote>
          </div>
          <br>
        </div>
        <div class="gmail_extra">If you only care to storing files
          needed for backup made at 00000000300000000C000000A3, you can
          remove 00000000300000000C000000A1 and
          00000000300000000C000000A2, but not the others.<br>
        </div>
        <div class="gmail_extra"><br clear="all">
        </div>
        <div class="gmail_extra">Regards,<br>
        </div>
        <div class="gmail_extra">-- <br>
          Matheus de Oliveira<br>
          Analista de Banco de Dados<br>
          Dextra Sistemas - MPS.Br nível F!<br>
          <a moz-do-not-send="true"
            href="http://www.dextra.com.br/postgres/" target="_blank">www.dextra.com.br/postgres</a><br>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------040907030909050104090405--