| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL as a local in-memory cache |
| Date: | 2010-06-29 17:27:34 |
| Message-ID: | 20972.1277832454@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> I asked on IRC and was told it is true, and looking at the C code it
>>> looks true. ?What synchronous_commit = false does is to delay writing
>>> the wal buffers to disk and fsyncing them, not just fsync, which is
>>> where the commit loss due to db process crash comes from.
>> Ah, I see. Thanks.
> I am personally surprised it was designed that way; I thought we would
> just delay fsync.
That would require writing and syncing to be separable actions. If
you're using O_SYNC or similar, they aren't.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-06-29 18:45:22 | Re: PostgreSQL as a local in-memory cache |
| Previous Message | Bruce Momjian | 2010-06-29 17:19:40 | Re: PostgreSQL as a local in-memory cache |