On Wed, May 23, 2001 at 11:39:15AM -0600, Chris Jones wrote:
> No, it could be any number of other things. The first that comes to
> mind is EINTR. How about something closer to:
Hmm. Actually, write(2) shouldn't return EINTR; it should return a
short read count. But other errno values inclu
Chris Jones <[EMAIL PROTECTED]> writes:
> No, it could be any number of other things. The first that comes to
> mind is EINTR. How about something closer to:
Writes to disk files don't suffer EINTR as far as I've ever heard
(if they do, there are an awful lot of broken programs out there).
Mor
On Wed, May 23, 2001 at 12:50:46PM -0400, Tom Lane wrote:
> errno = 0;
> if (write(...) != expectedbytecount)
> {
> int save_errno = errno;
>
> unlink(tmp);
>
> errno = save_errno ? save_errno : ENOSPC;
>
> elog(...)
"Oliver Elphick" <[EMAIL PROTECTED]> writes:
> I found the answer to this: the partition had filled up, and so the problem
> was lack of disk space.
> Could we have a more helpful error message?
Indeed. I don't like your solution however, since it's just papering
over the real problem which is
I found the answer to this: the partition had filled up, and so the problem
was lack of disk space.
Could we have a more helpful error message? I was just looking in the
wrong direction because of the contents of the message.
*** postgresql-7.1.1.orig/src/backend/access/transam/xlog.c Tue M
