Tom Lane wrote:
> Because, in fact, that is the usual reason for a short write. Do you
> have something better for the code to do?
Well, I would have liked to know the truth, such as
ERROR: short write on block blah
DETAIL: wrote %u bytes, %u requested
HINT: That might mean that the disk is full.
In our instance, there is no fullness problem. (The errors repeat too
inconsistently yet persistently for that.) Probably, the storage
device is improperly mounted (which could become the second half of the
hint), but I have to wait for test results.
In response to
pgsql-hackers by date
|Next:||From: Kevin Grittner||Date: 2006-11-28 19:49:31|
|Subject: Re: pg_dump -t broken for mixed case table names in|
|Previous:||From: Tom Lane||Date: 2006-11-28 19:43:17|
|Subject: Re: pg_dump -t broken for mixed case table names in beta3? |