Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D766F65011F for ; Fri, 5 Sep 2008 15:46:04 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 18203-06 for ; Fri, 5 Sep 2008 15:45:53 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D6B6D65013E for ; Fri, 5 Sep 2008 15:45:52 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m85IjnAo029355; Fri, 5 Sep 2008 14:45:49 -0400 (EDT) To: Arctic Toucan cc: pgsql-admin@postgresql.org Subject: Re: How can I avoid Frozenxid wraparound on failover to a standby(PITR) database? In-reply-to: References: <26690.1220633537@sss.pgh.pa.us> Comments: In-reply-to Arctic Toucan message dated "Fri, 05 Sep 2008 14:08:02 -0400" Date: Fri, 05 Sep 2008 14:45:49 -0400 Message-ID: <29354.1220640349@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/49 X-Sequence-Number: 30142 Arctic Toucan writes: > My standard settings in the config file are: > autovacuum_freeze_max_age = 2,000,000,000 > vacuum_freeze_min_age = 100,000,000 Ah, well, there's the issue. It could be expected that no tuple freezing would happen before autovacuum_freeze_max_age. I'd take a zero off that value I think --- you're not leaving yourself a lot of daylight between freeze_max_age and wraparound. You could get away with that setting in a smaller database that didn't take so long to vacuum, but in a bigger one you want to freeze a bit more aggressively IMHO. regards, tom lane