Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id AF43B37C369 for ; Tue, 30 Sep 2008 11:22:40 -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 43681-08 for ; Tue, 30 Sep 2008 11:22:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id 9072937BE54 for ; Tue, 30 Sep 2008 11:22:27 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 30 Sep 2008 09:22:24 -0500 Message-Id: <48E1EFC2.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.3 Date: Tue, 30 Sep 2008 09:22:10 -0500 From: "Kevin Grittner" To: Subject: Forcing new timelines Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200809/351 X-Sequence-Number: 30444 With our backup techniques, it is a bit painful to deal with WAL files when the number goes lower and starts re-using numbers already archived, as when we upgrade to a new release using pg_dumpall piped to psql. We can work around it, but it would keep our environment and scripts simpler (and therefore less fragile) if we could count on a later WAL file always having a name which sorts after any earlier file. I poked around the documentation, looking for a way that we could force the new cluster to use a WAL file name higher than the last, either within the some timeline or by bumping the timeline ID. The only thing I found is pg_resetxlog, which seems like kind of a big hammer to use on an otherwise sound database. Did I miss anything in the documentation? Any suggestions? -Kevin