| From: | Florian Weimer <fweimer(at)bfk(dot)de> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | 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:19:10 |
| Message-ID: | 82ski9e35d.fsf@mid.bfk.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* 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.
--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-06-09 17:21:35 | pgindent run coming |
| Previous Message | Andrew Dunstan | 2009-06-09 17:16:57 | Re: Not quite a security hole in internal_in |