Skip site navigation (1) Skip section navigation (2)

BUG #1672: Postgres 8.0 doesn't return errors.

From: "Gregory L Miller-Kramer" <millerg(at)contexttech(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1672: Postgres 8.0 doesn't return errors.
Date: 2005-05-16 13:16:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      1672
Logged by:          Gregory L Miller-Kramer
Email address:      millerg(at)contexttech(dot)com
PostgreSQL version: 8.0.2
Operating system:   CentOS 4.0
Description:        Postgres 8.0 doesn't return errors.

To Whom it may concern:
Postgres8 does not return errors for some reason. If you look at the errors
generated on dev or purposely cause an error in psql you will see what I
mean. All errors are being dumped to /opt/pgsql/pgstartup.log. I'm thinking
maybe this is a config option when postgres is built? Or maybe a bug in

I had originally thought this was fixed by removing the ">> $PGLOG" from the
the postgres startup script and restarting postgres. However, all that did
was dump errors to STDOUT rather than the log file, so it looked to me like
the problem was fixed. However, after I logged out of pgsql, I saw that I
was still getting errors on the console from other people and the apps, etc.
And when I closed my shell, all errors were lost, so I had to put the change
back so that we could at least find the errors in pgstartup.log if we need

When we used 7.4.2 we did not have this issue. The errors would disply in
psql as well as in the web page. We are using Apache, mod_perl, and

Thank you,
Greg Miller-Kramer


pgsql-bugs by date

Next:From: Tom LaneDate: 2005-05-16 16:52:24
Subject: Re: BUG #1670: pg_dump fails on CentOS 4
Previous:From: joshDate: 2005-05-16 12:16:49
Subject: Re: BUG #1670: pg_dump fails on CentOS 4

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group