Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eekqZ-0000g3-4g for pgsql-performance@arkaria.postgresql.org; Thu, 25 Jan 2018 16:57:55 +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 1eekqY-0006X5-EP for pgsql-performance@arkaria.postgresql.org; Thu, 25 Jan 2018 16:57:54 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eekqY-0006Wt-44 for pgsql-performance@lists.postgresql.org; Thu, 25 Jan 2018 16:57:54 +0000 Received: from mx1.mailbox.org ([80.241.60.212]) by makus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eekqV-0006Nk-6G for pgsql-performance@postgresql.org; Thu, 25 Jan 2018 16:57:52 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [80.241.60.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id 2B1DE42BB0; Thu, 25 Jan 2018 17:57:47 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp2.mailbox.org ([80.241.60.241]) by gerste.heinlein-support.de (gerste.heinlein-support.de [91.198.250.173]) (amavisd-new, port 10030) with ESMTP id F0rPJyFqNf-p; Thu, 25 Jan 2018 17:57:45 +0100 (CET) Message-ID: <1516899464.2419.1.camel@cybertec.at> Subject: Re: pg_xlog unbounded growth From: Laurenz Albe To: Stefan Petrea , "pgsql-performance@postgresql.org" Date: Thu, 25 Jan 2018 17:57:44 +0100 In-Reply-To: References: 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 Stefan Petrea wrote: > During some database imports(using pg_restore), we're noticing fast > and unbounded growth of pg_xlog up to the point where the > partition(280G in size for us) that stores it fills up and PostgreSQL > shuts down. What do you see in pg_stat_archiver? Yours, Laurenz Albe