BUG #4096: PG 8.3.1. confused about remaining disk space

The following bug has been logged online:

Bug reference:      4096
Logged by:          
Email address:      j6m@[EMAIL PROTECTED]
 version: 8.3.1
Operating system:   Linux
Description:        PG 8.3.1. confused about remaining disk space
Details: 

I ran today a legacy application with PG 8.3.1 on a test machine.

The DB is some ~30 MB. Default tables do have OIDs and BLCKSZ is set 
system-wide to 16384 (because of another DB).

A lot of messages like these do appear wich tend to indicate PG 8.3.1 is
confused. This set of SQL scripts used to run from PG 7.0.3 to PG 8.2.6
with
no problem.

WARNING:  could not create relation-cache initialization file 
"base/19693/pg_internal.init.29329": No space left on device
DETAIL:  Continuing anyway, but there's something wrong.
create temp table param0 (max0 date, datelb date) : ERROR:  could not
create

relation 1663/19693/634161: No space left on device
row number 0 is out of range 0..-1
row number 0 is out of range 0..-1
WARNING:  could not create relation-cache initialization file 
"base/19693/pg_internal.init.29330": No space left on device
DETAIL:  Continuing anyway, but there's something wrong.
create temp table param0 (max0 date, datelb date) : ERROR:  could not
create

relation 1663/19693/634162: No space left on device
row number 0 is out of range 0..-1
row number 0 is out of range 0..-1

Disk saturation, you think ? No at all, as in the meantime :

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3             9.9G  8.5G  874M  91% /
udev                  125M   88K  125M   1% /dev
/dev/sda1              54M   15M   37M  29% /boot
/dev/sda4             8.3G  7.4G  966M  89% /home
/dev/sdb1              38G   31G  7.2G  81% /var/lib/pgsql

As you can see, there is some 200 times the active DB size that remains 
available.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs