From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-admin@postgresql.org
Subject: Forcing new timelines
Date: Tue, 30 Sep 2008 09:22:10 -0500
Message-ID: <48E1EFC2.EE98.0025.0@wicourts.gov> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov
Subject: Re: Forcing new timelines
In-Reply-To: <48E1EFC2.EE98.0025.0@wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox