From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: mascarm@mascari.com
Cc: ZeugswetterA@spardat.at
Cc: pgsql-hackers@postgresql.org
Subject: Re: Point in Time Recovery
Date: Tue, 13 Jul 2004 10:29:44 -0400
Message-ID: <15780.1089728984@sss.pgh.pa.us> (raw)
In-Reply-To: <1089718702.17493.2527.camel@stromboli>
References: <1089060299.17493.58.camel@stromboli>
<4263.1089064016@sss.pgh.pa.us>
<1089150005.17493.270.camel@stromboli>
<1089718702.17493.2527.camel@stromboli>
Simon Riggs <simon@2ndquadrant.com> writes:
> Please tell me that we can ignore the state of the clog,
We can.
The reason that keeping track of timelines is interesting for xlog is
simply to take pity on the poor DBA who needs to distinguish the various
archived xlog files he's got laying about, and so that we can detect
errors like supplying inconsistent sets of xlog segments during restore.
This does not apply to clog because it's not archived. It's no more
than a data file. If you think you have trouble recreating clog then
you have the same issues recreating data files.
regards, tom lane
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: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, alvherre@dcc.uchile.cl, pgman@candle.pha.pa.us, mascarm@mascari.com, ZeugswetterA@spardat.at, pgsql-hackers@postgresql.org
Subject: Re: Point in Time Recovery
In-Reply-To: <15780.1089728984@sss.pgh.pa.us>
* 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