| From: | Chris Watson <opsys(at)voodooland(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql-server/src backend/storage/buffer/bufmgr ... |
| Date: | 2004-01-28 00:34:15 |
| Message-ID: | B3A99E92-5129-11D8-A471-0003937B4040@voodooland.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Jan 27, 2004, at 6:25 PM, Tom Lane wrote:
> Perhaps more to the point: all this is predicated on an assumption no
> longer particularly valid, which is that the kernel's ideas about disk
> write scheduling matter at all. A decent SCSI disk drive will pre-empt
> the kernel's ideas anyway by absorbing as many pending writes as it can
> and then doing its own write scheduling. fsync won't affect the
> drive's
> choices in the least, only allow us to find out when the drive is done.
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
Perhaps totally unrelated, as i've only read the last couple of posts
on this, but what does Postfix (the MTA) do? How does it handle this?
I trust Wietse implicitly to DTRT. If it were me I would ask him how he
handles the writes or at least check the Postfix src. *shrug* Just an
idea.
Chris Watson
M.M.
Bestor G. Brown #433
Wichita, KS
AIM: BSDUNIX44
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-01-28 07:46:44 | pgsql-server/src/backend/parser parse_agg.c |
| Previous Message | Tom Lane | 2004-01-28 00:25:28 | Re: pgsql-server/src backend/storage/buffer/bufmgr ... |