From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql-server/src backend/storage/buffer/bufmgr ... |
Date: | 2004-01-26 20:17:38 |
Message-ID: | 14634.1075148258@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Not necessarily --- it could be out-of-disk-space, on at least some
>> filesystems. More to the point, the important thing is not to commit a
> I assume the operating system is already allocating file system space
> during the write, and the sync is only forcing it to disk.
Not so --- as was pointed out later in the thread, neither NFS nor AFS
work that way, and there could be other cases.
In any case, I don't subscribe to the idea that we can just abdicate all
responsibility in case of hardware problems. Yes, we do rely on a disk
to keep storing information once it's accepted it, but that doesn't mean
that it's okay to ignore write-failure reports. We are failing to hold
up our end of the deal if we do that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-01-26 20:44:38 | Re: pgsql-server/src backend/storage/buffer/bufmgr ... |
Previous Message | Bruce Momjian | 2004-01-26 20:10:41 | Re: pgsql-server/src backend/storage/buffer/bufmgr ... |