Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hiPxv-0000Kr-Od for pgsql-admin@arkaria.postgresql.org; Tue, 02 Jul 2019 21:05:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hiPxu-0006pU-LK for pgsql-admin@arkaria.postgresql.org; Tue, 02 Jul 2019 21:05:26 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hiPxu-0006pN-60 for pgsql-admin@lists.postgresql.org; Tue, 02 Jul 2019 21:05:26 +0000 Received: from mail-qt1-x841.google.com ([2607:f8b0:4864:20::841]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hiPxr-0005Gl-8A for pgsql-admin@postgresql.org; Tue, 02 Jul 2019 21:05:25 +0000 Received: by mail-qt1-x841.google.com with SMTP id h21so90095qtn.13 for ; Tue, 02 Jul 2019 14:05:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=gL/6ZI9HX+aCWyguELBVWDNcMFkLGJ16vrBC5BhbxOk=; b=DiwO9+gqcUhZOR1SekY2SgZpraCw1IMOO2UMAvFqsBjvgLIVP59lbEFZPXz2dRfHoL MbuGVRrVloYB2QaT5soVq1p/7iYOsfmiKcTOazGmUqc3PttuEqfbCnoHLpTUrD684Fow 4VuVGrUhFWXj6pcLEhXgCo0LBPd0je5XKcrBDcm7eudjWxD4cIpYl3b9HXYMvOIXt/Pb 3p8o0ixL02TGgeRxhg8Moo9gJJLzZuxaK0SQp4fRcM81PMqOGAu7BoBffjUjlBOFdlvt pY5vASjDKlEIk4f1j7PRixzWtacebDRNQ37JZGzBBhupekzX816hGzwv+dNnamdTwL8X pMmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=gL/6ZI9HX+aCWyguELBVWDNcMFkLGJ16vrBC5BhbxOk=; b=cqGd3bnuewGARJKyAIuSzrUd5nuEEAz6HjdTHtFtx/GqTmfDME6HQeS/xw9XkU6C0x hxXaCTYDdE4nhF+X1kuxLZwbId1PX4ZBx/DQjeyaWapzOeUhquyi1AWtRIuYRUESf4Xa 6OFD2r5VEbhmLwdEELbH60wMKeVlO8PSAsPdkV8kWIiqr8DdDGmHCPG7+bkRUHLpYtVQ ofJ48kqwFq0iqY79wdHpmAu15ToSN+VHGMt78+V3fa5XG2OXNYDkPxm/iXSf++m71D8x UAjoQCpDTySqGAYdQoTtkWZr0MEvLXbSJQMj65v/fB62ke9c2XVFOfRSXoPGN5pMLQQB yxmQ== X-Gm-Message-State: APjAAAXgEYtO3CegUN+r4xBKHgwUM7YDwceVS1CGV6wozzPaavzTOpuS TdJ0HekwsPUgxozM/54YBIEHBQ== X-Google-Smtp-Source: APXvYqz0/dVuR3A4g7cs/DBIZHXLGYbYDxzNjJNMwm/zKfx4GCoXhcJf6fXwcgBD8IQLZHmPHbEYWQ== X-Received: by 2002:ac8:156:: with SMTP id f22mr26678549qtg.58.1562101521280; Tue, 02 Jul 2019 14:05:21 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id f68sm34420qtb.83.2019.07.02.14.05.19 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Tue, 02 Jul 2019 14:05:20 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 9EF7E120A9D; Tue, 2 Jul 2019 17:05:17 -0400 (-04) Date: Tue, 2 Jul 2019 17:05:17 -0400 From: Alvaro Herrera To: Mark Steben Cc: pgsql-admin Subject: Re: pg_xlog no longer rotating out Message-ID: <20190702210517.GA30568@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Jul-02, Mark Steben wrote: > Good afternoon, > We run postgres 9.4 with hot standby streaming replication. We have been > running abnormally high updates and the pg_xlogs have queued to about 80 > percent of disk capacity. This often happens and the network is not fast > enough to handle the transfer of logs to the replicated server. > What I have done in the past, and done again today is to change the > archive_command from the script that scp's the logs to '/bin/true'. This > stops the logship and allows the normal pg_xlog rotation to catch up. Did you "pg_ctl reload" after changing the config file? Maybe you have an inactive (or otherwise not advancing) replication slot? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services