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

2005-12-28 Thread Frank van Vugt
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

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

2005-12-28 Thread Tom Lane
Frank van Vugt [EMAIL PROTECTED] writes: 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). See

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

2005-12-28 Thread Vivek Khera
On Dec 28, 2005, at 9:46 AM, Frank van Vugt wrote: 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.

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

2005-12-28 Thread Jim C. Nasby
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 [EMAIL PROTECTED]:47]~:21%tail -n 2 /opt/local/var/log/pgsql8/postgres.log ERROR: syntax error at or near 2 at character 10