Re: Multicolumn index corruption on 8.4 beta 2

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Florian Weimer <fweimer(at)bfk(dot)de>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Floris Bos / Maxnet <bos(at)je-eigen-domein(dot)nl>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Multicolumn index corruption on 8.4 beta 2
Date: 2009-06-09 17:37:35
Message-ID: 20090609173734.GF5938@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Florian Weimer wrote:
> * Josh Berkus:
>
> > Our documentation has been clear, back to version 7.0, that turning
> > fsync=off carries the risk that you will have to recreate your entire
> > database in the event of unexpected shutdown. That's not new.
>
> The documentation does not say this. Instead, there's the following
> rather explicit explanation that only OS crashes matter:
>
> | (Crashes of the database software itself are not a risk factor
> | here. Only an operating-system-level crash creates a risk of
> | corruption.)
>
> If it really matters how PostgreSQL is shut down in "fsync = off" mode
> (while the operating system keeps running), the documentation is
> seriously wrong here.

Yeah, AFAICT the writes are handed off to the operating system (just not
synced), so if it flushes its caches sanely at all there shouldn't be a
problem.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-06-09 17:38:51 Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7
Previous Message Robert Haas 2009-06-09 17:37:07 Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7