From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: List pgsql-patches <pgsql-patches@postgresql.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: [PATCHES] Infrastructure changes for recovery
Date: Thu, 18 Sep 2008 15:24:55 +0100
Message-ID: <1221747895.3913.2432.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <18549.1221746983@sss.pgh.pa.us>
References: <1218109459.4549.423.camel@ebony.2ndQuadrant>
<1220213074.4371.173.camel@ebony.2ndQuadrant>
<1905.1220895241@sss.pgh.pa.us>
<1221080797.3913.768.camel@ebony.2ndQuadrant>
<15776.1221594318@sss.pgh.pa.us>
<1221725145.3913.2315.camel@ebony.2ndQuadrant>
<16992.1221743196@sss.pgh.pa.us>
<1221745847.3913.2408.camel@ebony.2ndQuadrant>
<18549.1221746983@sss.pgh.pa.us>
On Thu, 2008-09-18 at 10:09 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > On Thu, 2008-09-18 at 09:06 -0400, Tom Lane wrote:
> >> Do we really need a checkpoint there at all?
>
> > "Timelines only change at shutdown checkpoints".
>
> Hmm. I *think* that that is just a debugging crosscheck rather than a
> critical property. But yeah, it would take some close investigation,
> which maybe isn't warranted if you have a less-invasive solution.
The important thing is that everybody uses the new timelineid.
AFAICS we actually write new timelineids into the WAL file if the
previous timelineid, so it can't be that risky.
Ignore v5 then and look for v6 on Monday. Hopefully the final one :-)
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
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-patches@postgresql.org
Cc: simon@2ndQuadrant.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] Infrastructure changes for recovery
In-Reply-To: <1221747895.3913.2432.camel@ebony.2ndQuadrant>
* 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