Re: just an inconvenience, or.... : failed queries don't appear in the log anymore since v8.?.?

decibel=# set log_min_error_statement=error;
SET
decibel=# select 1 2;
ERROR:  syntax error at or near "2" at character 10
LINE 1: select 1 2;
                 ^
decibel=# \q
decibel@phonebook.1[11:47]~:21%tail -n 2 /opt/local/var/log/pgsql8/postgres.log
ERROR:  syntax error at or near "2" at character 10
STATEMENT:  select 1 2;
decibel@phonebook.1[11:47]~:22%

On Wed, Dec 28, 2005 at 03:46:23PM +0100, Frank van Vugt wrote:
> Hi,
>
> I may be overlooking some option here, but somewhere between the v7 series and
> the current v8.1.1 that I'm using, failed queries stopped being logged, only
> the error message appears in the log (config option log_statement = all).
>
> I.e. executing
>
>     select 1 2;
>
> will result in just the logging of
>
>     ERROR:  syntax error at or near "2" at character 10
>
> Earlier versions logged the failed query as well, which made it a lot easier
> to cut&paste queries generated by applications in development in order to
> hunt down the problem.
>
> - psql follows up on the error by printing the line where it occured
>
> - setting log_error_verbosity to 'verbose' doesn't log the query itself either
>
>
> Is there a way to get the failed query into the log, or should it have been
> there in the first place?
>
>
>
>
>
> --
> Best,
>
>
>
>
> Frank.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461