Philip Warner <[EMAIL PROTECTED]> writes:
> There are a few places to check, but a lot less than before. Assuming I
> should just die on any failed write (which seems reasonable),
Yes, I see no point in continuing after a write failure. Just print
the strerror() message and exit.
> how do I
> c
At 20:50 4/01/01 -0500, Tom Lane wrote:
>
>Talk to Philip Warner about detecting output write failures. I think
>this might be a lot easier in current sources than it would have been in
>7.0.* or before; the actual I/O is more centralized, and I think you
>could reasonably hope to check for write
Matthew <[EMAIL PROTECTED]> writes:
> I posted a note to the hackers list about this very issue last week. It was
> never responded to. I am prepared to do the work and submit a patch, but I
> wanted some input on how best to do it. We had a problem with a backup
> script silently failing when
At 19:14 4/01/01 -0600, Matthew wrote:
>I posted a note to the hackers list about this very issue last week. It was
>never responded to. I am prepared to do the work and submit a patch, but I
>wanted some input on how best to do it. We had a problem with a backup
>script silently failing when t
I posted a note to the hackers list about this very issue last week. It was
never responded to. I am prepared to do the work and submit a patch, but I
wanted some input on how best to do it. We had a problem with a backup
script silently failing when the disk was full. I guess I will get start
