Re: Unlogged tables, persistent kind

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unlogged tables, persistent kind
Date: 2011-04-25 01:36:01
Message-ID: BANLkTi=5=N6+ync7b+ng1tvhzY5HNGvtZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 24, 2011 at 11:15 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> IMHO deleting all the data is a surprising option that will
> cause many people to curse us. I don't see preserving some of the data
> as being worse.

What possible damage to you want to recover from?

Without WAL logging after a software crash it's possible for update
chains to be broken, for multiple copies of the same tuple to be
visible, for some tuples to disappear but not others, etc.

And without checksums after a hardware crash it'll be possible for
pages to be torn resulting in tuple pointers that land in the middle
of nowhere or tuples that start off fine but are half overwritten with
unrelated garbage.

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Farina 2011-04-25 02:06:06 Re: fsync reliability
Previous Message Daniel Farina 2011-04-25 01:14:55 Re: fsync reliability