Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XR2PJ-0003D4-NJ for pgsql-admin@arkaria.postgresql.org; Mon, 08 Sep 2014 17:07:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XR2PI-0002YY-Pe for pgsql-admin@arkaria.postgresql.org; Mon, 08 Sep 2014 17:07:12 +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 1XR2PG-0002YG-If for pgsql-admin@postgresql.org; Mon, 08 Sep 2014 17:07:10 +0000 Received: from resqmta-po-12v.sys.comcast.net ([2001:558:fe16:19:96:114:154:171]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XR2PA-0007a8-Ky for pgsql-admin@postgresql.org; Mon, 08 Sep 2014 17:07:08 +0000 Received: from omta13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by resqmta-po-12v.sys.comcast.net with comcast id ogFc1o00317UAYk01h6zYt; Mon, 08 Sep 2014 17:06:59 +0000 Received: from jerry.enova.com ([38.98.177.132]) by omta13.emeryville.ca.mail.comcast.net with comcast id oh6l1o00K2rmZlA8Zh6o9F; Mon, 08 Sep 2014 17:06:56 +0000 Received: by jerry.enova.com (Postfix, from userid 1001) id 82ABD7401ED; Mon, 8 Sep 2014 12:06:45 -0500 (CDT) From: Jerry Sievers To: Alexey Klyukin Cc: bricklen , "pgsql-admin\@postgresql.org" Subject: Re: Standby is not removing restored WAL segments References: Date: Mon, 08 Sep 2014 12:06:45 -0500 In-Reply-To: (Alexey Klyukin's message of "Mon, 8 Sep 2014 16:18:57 +0200") Message-ID: <86y4tudot6.fsf@jerry.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1410196019; bh=nwuGYsEn16z5KzMRcEk+IIUcSuYu4K/Rd+BZQRPhL0o=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=YKz8PaA3NsHo4nNjJr3rKMU2oXNqN41eBYPMBz7xyKfeYIOCubzddq6IS/hYIG4Zk I41xGJzPs2KnlDZcfHkK9HJ1gl2pBrKDj66LM4HawX4A/l8Z4LG1tVUJt05aaIin48 kIcULOODNHIMU0LIYWxLv3N12HR85DYr5n2l8NIXyP09TyT8WrHgZGU7Lbudkz8fnX v9iyGjPb6xENpOCFUOz+Gn8z8qTcAKvEj61O/gMD5oUNQD9cWGj5AeF9FBpVew5XoP e3IbHJ9HV3u36FimJSo6aHKEutes/5RtCYZTr8rPciwlhVbPSegLRwZaz//VaAzXNv kmhVjsac9HsDQ== X-Pg-Spam-Score: -3.2 (---) 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 Alexey Klyukin writes: > On Mon, Sep 8, 2014 at 3:52 AM, bricklen wrote: > >> >> On Fri, Sep 5, 2014 at 12:33 AM, Alexey Klyukin wrote: >>> >>> We've got a 9.3.5 DB running in a standby mode for a fairly large DB >>> (500GB) with a busy WAL traffic (couple of GBs per hour) and it >>> occasionally 'forgets' to remove the segments it restored. >> >> >> A complete shot in the dark, but do you take backups from that server, and >> if so, does the backup script "pause" replication via >> "pg_xlog_replay_pause()"? If so, "select pg_is_xlog_replay_paused();" should >> return true, and executing "select pg_xlog_replay_resume()" will un-pause >> replication. > > > >> >> Again, that's only a WAG. >> > > Thanks. we do take DB backups from this server, but not from this > cluster on it, so it's not a backup interference. Or... Are your backups being taken using rsync or any non-pg_basebackup method *and* you are copying unnecessary WALs to the target new standby server, which then lay around forever as artifacts of not having been omitted initially? > > -- > Regards, > Alexey Klyukin -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin