| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | flyusa2010 fly <flyusa2010(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: disk caching for writing log |
| Date: | 2010-12-03 17:43:13 |
| Message-ID: | 4CF92C31.104@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03.12.2010 13:49, flyusa2010 fly wrote:
> When writing log, dbms should synchronously flush log to disk. I'm
> wondering, if it is possible that the logs are in disk cache, while the
> control is returned to dbms again, so dbms thinks logs are persistent on
> disk. In this case, if the disk fails, then there's incorrectness for dbms
> log writing, because the log is not persistent, but dbms considers it is
> persistent!
I have no idea what you mean. The method we use to flush the WAL to disk
should not be fallible to such failures, we wait for fsync() or
fdatasync() to return before we assume the logs are safely on disk. If
you can elaborate what you mean by "control is returned to dbms", maybe
someone can explain why in more detail.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2010-12-03 18:14:20 | Re: disk caching for writing log |
| Previous Message | Andrew Dunstan | 2010-12-03 17:37:11 | Re: WIP patch for parallel pg_dump |