Hello,
I'm using PostgreSQL 7.1.2 on Sun Solaries 8.

One day when EMS server was kept for overnight test machine ran out of
disk space. This tied up the postgres process and stoped normal use of
the EMS. The postgres logs have useful info explaining the situation but
it looks as if this information is not passed to the client.
I want to display client warning to the user when the server/db
hostmachine is running low on disk space. The warning could be displayed
to any open clients as well as any new clients who attempt to log into
the server.

Please see the server logs and the postgres logs attached.

Here is the scenario:

The EMS server was kept running for 2 days, 12 hours, for overnight
test. Machine ran out of disk space. This tied up the postgres process
and stoped normal use of the EMS. The postgres logs have useful info
explaining the situation but it looks as if this information is not
passed to the client.
I want to display client warning server/db hostmachine is running low on
disk space. The warning could be displayed to any open clients as well
as any new clients who attempt to log into the server.
When a new user tried to login to the server, authentication failed.

On the EMS server hostmachine I could not su 'postgres' to see the
postgres pid.
It looked as if the postgres process was tied up some how.

The EMS server pids were available but postgress was not. This looks
like a potential DB crash although there are no postgres core files or
logs that give us clues as to what may have happned
The zipped server logs display lots of error trying to locate the
postgres PID.

The snapshot of the Postgres log is like this:
ERROR: cannot extend trap: No space left on device.
Check free disk space.
ERROR: cannot extend trap: No space left on device.
Check free disk space.
ERROR: cannot extend trap: No space left on device.
Check free disk space.
ERROR: cannot extend trap: No space left on device.

"root" execution of the PostgreSQL server is not permitted.

The server must be started under an unprivileged userid to prevent
a possible system security compromise. See the INSTALL file for
more information on how to properly start the server.

DEBUG: database system shutdown was interrupted at 2003-02-10 06:32:20
PST
DEBUG: CheckPoint record at (0, 98945120)
DEBUG: Redo record at (0, 98945120); Undo record at (0, 0); Shutdown
FALSE
DEBUG: NextTransactionId: 221802; NextOid: 239904
DEBUG: database system was not properly shut down; automatic recovery
in progress...
DEBUG: redo starts at (0, 98945184)
DEBUG: ReadRecord: record with zero len at (0, 98962280)
DEBUG: redo done at (0, 98962240)
DEBUG: database system is in production state
DEBUG: MoveOfflineLogs: remove 0000000000000005

Is there anyway, that Postgres returns error code (apart from error
message) when disk space is full ?
Pls. help ASAP.

Thanks,
Anagha