| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Ram Ravichandran" <ramkaka(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org(dot) |
| Subject: | Re: turning fsync off for WAL |
| Date: | 2008-06-03 01:09:08 |
| Message-ID: | dcc563d10806021809k6c0fdee1k8a70b674aa05c9f1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 2, 2008 at 6:42 PM, Ram Ravichandran <ramkaka(at)gmail(dot)com> wrote:
>
>> Running without fsyncs is likely to lead to a corrupted db if you get
>> a crash / loss of connection etc...
>
> Just to clarify, by corrupted db you mean that all information (even the
> ones prior to the last fsync) will be lost. Right?
Well, it might be there, might not. more likely most of it will be
there, but you'll get errors accessing files and could have incoherent
data coming out of the db.
but yeah, it's way more than just losing the last transaction.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2008-06-03 01:12:36 | Re: turning fsync off for WAL |
| Previous Message | Ram Ravichandran | 2008-06-03 00:42:44 | Re: turning fsync off for WAL |