Gregory L Miller-Kramer <[EMAIL PROTECTED]> writes:
> I entered the statement you wanted. (show client_min_messages;) It
> returned...
> client_min_messages
> -
> log
> (1 row)
[ scratches head... ] It's pretty hard to see why SHOW would display
something but error messages
Thanks again for getting back to me.
I entered the statement you wanted. (show client_min_messages;) It returned...
client_min_messages
-
log
(1 row)
I did try what you mentioned (set client_min_messages to notice;) and it didn't work.
Any other recommendations? I do ap
On Wed, May 18, 2005 at 09:11:00AM -0400, Gregory L Miller-Kramer wrote:
>
> I entered the statement you wanted. (show client_min_messages;) It
> returned...
> client_min_messages
> -
> log
> (1 row)
>
> I did try what you mentioned (set client_min_messages to notice;) and it
On Tue, May 17, 2005 at 05:05:03PM -0400, Gregory L Miller-Kramer wrote:
> On system One I enter the database ...
> psql exdb exdb
> select misspelled_excol from extable;
>
> and an error is displayed...
> ERROR: column 'misspelled_excol' does not exist
>
> On the "Other" system (Postgres 8.0) t
"Gregory L Miller-Kramer" <[EMAIL PROTECTED]> writes:
> 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.
This report is pretty uncl
On Mon, May 16, 2005 at 02:16:34PM +0100, Gregory L Miller-Kramer wrote:
>
> Postgres8 does not return errors for some reason.
In what context?
> If you look at the errors generated on dev or purposely cause an
> error in psql you will see what I mean.
Please provide an example so we can see exa