Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XW4rm-0003iB-Jc for pgsql-admin@arkaria.postgresql.org; Mon, 22 Sep 2014 14:45:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XW4rm-0005cR-2R for pgsql-admin@arkaria.postgresql.org; Mon, 22 Sep 2014 14:45:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XW4rl-0005ag-3o for pgsql-admin@postgresql.org; Mon, 22 Sep 2014 14:45:25 +0000 Received: from mail-yk0-x22e.google.com ([2607:f8b0:4002:c07::22e]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XW4rX-0002pN-QM for pgsql-admin@postgresql.org; Mon, 22 Sep 2014 14:45:24 +0000 Received: by mail-yk0-f174.google.com with SMTP id q9so706670ykb.5 for ; Mon, 22 Sep 2014 07:45:09 -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 :content-type:content-transfer-encoding; bh=gT2PbRUXDnrp9vdiMTQnJv9rxbODHn7QtZFJI565EU4=; b=EBkH96UFfAaXhLJ+e2MRwe89AyMeK8dHK0okzGGufETf5o/Phk85hi2JrBRP1+U6Mx yWCwhHKqs+HfG1bV0dwidXdZbspIdCYxBqV3Q4mVodwBRw3k4bwYsklWWqRylKs6Bcic IYItY4mzp1DaHn/dIjuXgUfXNPtfJFjhdN5Wim+pjWbG2EFmEFckYKX/FyDh8nNuWgLj JmorhdRETqmTjechcXOqxKC4QKrBsOAKdGxmWQWlUJQqFkRthb9GcRFaiC86I994RWsK M61jT9GMMHbMtzCMjiWEAxcD31ZaDqNlawl8YyrbwfCHWxUatvIpxJzayfaVeMSPyy0m TbNQ== X-Received: by 10.236.161.66 with SMTP id v42mr863502yhk.117.1411397109175; Mon, 22 Sep 2014 07:45:09 -0700 (PDT) Received: from [192.168.254.1] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id d32sm4464854yhq.29.2014.09.22.07.45.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Sep 2014 07:45:08 -0700 (PDT) Message-ID: <542035E7.5080207@gmail.com> Date: Mon, 22 Sep 2014 10:44:55 -0400 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: When is it safe to remove backup files from a wal archiving directory Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Hi all, I've noticed that my standby servers never bother to delete a wal backup file from the archiving directory. In fact, they never even try to copy it out of the directory, and after a while, I may see over a dozen files like: 000000040000000A000000F9.backup 000000040000000C00000003.backup etc. The youngest of these files is from last Friday afternoon, and these rest go back over 6 weeks. Being this is a streaming replication standby, I probably don't need them at all, but I've been keeping them as insurance policies. Question is how many, if any, do I need to keep? -- Jay -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin