Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1egnlf-0001LX-Rk for pgsql-admin@arkaria.postgresql.org; Wed, 31 Jan 2018 08:29:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1egnlf-0006aG-0q for pgsql-admin@arkaria.postgresql.org; Wed, 31 Jan 2018 08:29:19 +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 1egnle-0006a7-Pv for pgsql-admin@lists.postgresql.org; Wed, 31 Jan 2018 08:29:18 +0000 Received: from mx2.mailbox.org ([80.241.60.215]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1egnlc-0000lF-DA for pgsql-admin@lists.postgresql.org; Wed, 31 Jan 2018 08:29:18 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id 1DAE041139; Wed, 31 Jan 2018 09:29:15 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by hefe.heinlein-support.de (hefe.heinlein-support.de [91.198.250.172]) (amavisd-new, port 10030) with ESMTP id AFmJ1tjLfUhU; Wed, 31 Jan 2018 09:29:13 +0100 (CET) Message-ID: <1517387352.2579.8.camel@cybertec.at> Subject: Re: pg_xlog piling From: Laurenz Albe To: chris , pgsql-admin@lists.postgresql.org Date: Wed, 31 Jan 2018 09:29:12 +0100 In-Reply-To: <575c1026-aabd-4854-55f7-1292c57b3da6@pgsqlrocket.com> References: <575c1026-aabd-4854-55f7-1292c57b3da6@pgsqlrocket.com> Organization: Cybertec Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk chris wrote: > I have a standby that is in replication only mode but the pg_xlog > directory is currently at 577GB utilized and is growing daily and I > can't figure out why. This was a problem before when we were on > postgresl 9.2 but changed some postgresql.conf parameters and then > rebuilt it but still running into the same problem. What do you get on the primary for SELECT state, sent_location, write_location, flush_location, replay_location FRPM pg_stat_replication; Yours, Laurenz Albe