Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1axGAb-0003Li-Hu for pgsql-admin@arkaria.postgresql.org; Mon, 02 May 2016 15:54:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1axGAa-0001Mj-Ef for pgsql-admin@arkaria.postgresql.org; Mon, 02 May 2016 15:54:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1axGAZ-0001MS-VU for pgsql-admin@postgresql.org; Mon, 02 May 2016 15:54:00 +0000 Received: from gw-mail1.roc.in.bccnetworks.net ([184.12.4.101]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1axGAW-0005Wa-8B for pgsql-admin@postgresql.org; Mon, 02 May 2016 15:53:59 +0000 Received: from localhost (localhost [127.0.0.1]) by gw-mail1.roc.in.bccnetworks.net (Postfix) with ESMTP id 67A184027CEA for ; Mon, 2 May 2016 11:53:53 -0400 (EDT) Received: from gw-mail1.roc.in.bccnetworks.net ([127.0.0.1]) by localhost (gw-mail1.roc.in.bccnetworks.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id RYlgNorF8xTP for ; Mon, 2 May 2016 11:53:52 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by gw-mail1.roc.in.bccnetworks.net (Postfix) with ESMTP id 70E5944F3DB4 for ; Mon, 2 May 2016 11:53:52 -0400 (EDT) X-Virus-Scanned: amavisd-new at bccglobal.com Received: from gw-mail1.roc.in.bccnetworks.net ([127.0.0.1]) by localhost (gw-mail1.roc.in.bccnetworks.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id bEHJPU-IGSMf for ; Mon, 2 May 2016 11:53:52 -0400 (EDT) Received: from gw-mail1.roc.in.bccnetworks.net (localhost [127.0.0.1]) by gw-mail1.roc.in.bccnetworks.net (Postfix) with ESMTP id 528DB456CD6D for ; Mon, 2 May 2016 11:53:52 -0400 (EDT) Date: Mon, 2 May 2016 11:53:52 -0400 (EDT) From: Peter =?utf-8?Q?Brunnengr=C3=A4ber?= Reply-To: Peter =?utf-8?Q?Brunnengr=C3=A4ber?= To: pgsql-admin@postgresql.org Message-ID: <1206916146.2714.1462204427454.JavaMail.pbrunnen@Station8.local> In-Reply-To: <1768734441.2711.1462204088868.JavaMail.pbrunnen@Station8.local> Subject: Hot_standby WAL archiving question MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailer: Zimbra 8.6.0_GA_1194 (Zimbra Desktop/7.2.7_12059_Mac) Thread-Topic: Hot_standby WAL archiving question Thread-Index: ntFbG24DQ/nAyUPc+9hvYqq3dB2oMg== X-Pg-Spam-Score: -1.9 (-) 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 Hello all, So I have been working on setting up an active/standby clustered postgres= ql 9.2 using corosync. The corosync documentation has me enable WAL archi= ving "archive_command =3D 'cp %p /db/data/postgresql/9.2/pg_archive/%f'" I assume so that the secondary can catch up in async (log shipping) mode = before going into sync (streaming) mode. But I am noticing as I push data = through the DB, that my pg_archive keeps growing and I am worried about run= ning out of disk space. Per the postgresql documentation, I set "wal_keep_segments" but I believe= this only effects the segments in the pg_xlog and not what the archive_com= mand is processing. So, since I am not keeping the archived WAL statements for long term use,= is it safe to set "archive_cleanup_command =3D 'pg_archivecleanup /db/data= /postgresql/9.2/pg_archive %r'" on the master? Also will the archive clean= up command even have effect? I only read about it being on slaves to clean= -up what has already been processed. Thank you! -With kind regards, Peter Brunnengr=C3=A4ber --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin