From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Avoiding adjacent checkpoint records |
Date: | 2012-06-07 16:00:24 |
Message-ID: | CA+U5nM+S0Sj=nrqFVBA7knRrLqvLFNSDidM1vML03uGogbyDNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7 June 2012 14:59, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> there is no guarantee that we'll manage to reach a database state
>> that is consistent with data already flushed out to disk during
>> the last checkpoint.
>
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> I know of real customers who would have suffered real data loss
>> had this code been present in the server version they were using.
>> Checkpoints are the *only* mechanism by which SLRU pages get
>> flushed to disk on a mostly-idle system. That means if something
>> happens to your pg_xlog directory, and you haven't had a
>> checkpoint, you're screwed.
If that is the concern, then its a one line fix to add the missing clog flush.
The other suggestions I've skim read seem fairly invasive at this
stage of the release.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2012-06-07 16:02:12 | Re: XLog changes for 9.3 |
Previous Message | Andres Freund | 2012-06-07 15:57:50 | Re: Ability to listen on two unix sockets |