| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Jack Orenstein <jao(at)geophile(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Trying to minimize the impact of checkpoints |
| Date: | 2004-06-13 02:16:02 |
| Message-ID: | 20766.1087092962@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>> [sync before fsync]
> Not a good idea on some systems. From the linux sync(2) manpage:
> BUGS
> According to the standard specification (e.g., SVID), sync()
> schedules the writes, but may return before the actual writing
> is done. However, since version 1.3.20 Linux does actually
> wait.
This is another reason why it would have to be optional: the win comes
only if the kernel adheres literally to the SVID specification for
sync(2). I think all the BSDen do, and HPUX seems to, but there are
undoubtedly platforms that don't.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2004-06-13 05:19:08 | Re: Release 7.4.3 branded |
| Previous Message | Martijn van Oosterhout | 2004-06-13 00:26:31 | Re: Trying to minimize the impact of checkpoints |