"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> We haven't used tablespace features yet, as 3 of the 4 databases
> running PostgreSQL so far are on Windows. We have run out of space a
> couple times, and it seems like it handles it well in terms of not
> corrupting the database, and resuming OK once some space is freed. The
> messages are not that clear -- some sort of generic I/O write error, as
> I recall, instead of "out of disk space" being clearly stated.
Hm, this may be an issue of poor translation of Windows error codes;
AFAIR PG is pretty good these days about reporting the correct error
message on Unix. Can you dig up the exact message you got, or
deliberately reproduce the problem to get a fresh copy?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
