Re: New PostgrSQL Errors

From: Dror Matalon <dror(at)zapatec(dot)com>
To: Postgres <sfpug(at)postgresql(dot)org>
Subject: Re: New PostgrSQL Errors
Date: 2004-03-19 01:14:15
Message-ID: 20040319011415.GB1757@rlx11.zapatec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: sfpug

Looks like out of the box you should get:
#log_error_verbosity = default # terse, default, or verbose messages
which is what we have which results in log/pglog in messages that look
like this:

....
Mar 18 17:02:09 <local0.warn> eight postgres[62319]: [18-1] ERROR: unterminated quoted string at or near "'The admin team has picked the starting 10 man ro ster to represent the Regular"
Mar 18 17:02:09 <local0.warn> eight postgres[62319]: [18-2] at character 232
Mar 18 17:02:09 <local0.err> eight postgres[62319]: [19-1] FATAL: invalid frontend message type 32

If you want to be explicit about this, you can set
log_statement = true

which will log *every* statement that postgress sees.

On Thu, Mar 18, 2004 at 04:50:07PM -0800, David Wheeler wrote:
> On Mar 18, 2004, at 4:31 PM, Dror Matalon wrote:
>
> >A more detailed error message telling you what these are should show up
> >in log/pglog. Might depend on your logging setting in postgres.conf
> >though.
>
> Maybe, but I can't figure out how. I turned on a bunch of syslog stuff,
> but nothing appeared...
>
> Regards,
>
> David
>

--
Dror Matalon
Zapatec Inc
1700 MLK Way
Berkeley, CA 94709
http://www.fastbuzz.com
http://www.zapatec.com

In response to

Responses

Browse sfpug by date

  From Date Subject
Next Message David Wheeler 2004-03-19 04:43:39 Re: New PostgrSQL Errors
Previous Message David Wheeler 2004-03-19 00:50:07 Re: New PostgrSQL Errors