[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Disaster!
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2004-01-31 4:54:45
Message-ID: 26500.1075524885 () sss ! pgh ! pa ! us
[Download RAW message or body]

Randolf Richardson <rr@8x.ca> writes:
> "gsstark@mit.edu (Greg Stark)" stated in
> comp.databases.postgresql.hackers: 
>> The traditional Unix filesystems certainly don't return errors at close.

>     	Why shouldn't the close() function return an error?  If an invalid 
> file handle was passed to it, it most certainly should indicate this 

Of course.  We're discussing the situation where no errors were reported
in prior syscalls --- in particular, open() succeeded.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to majordomo@postgresql.org so that your
      message can get through to the mailing list cleanly
[prev in list] [next in list] [prev in thread] [next in thread]