Re: [BUGS] [EMAIL PROTECTED]: BUG in logs]
OK, you're right about the log_min_error_statement value, but this behaviour has changed from 8.0. In earlier versions ERROR statements did get logged if log_statment was set to all or in 7.4, set to "on" DMaybe I missed something in the changelog of 8.1? On Tue, 11 Apr 2006 23:51:51 +0200, "Guillaume Smet" <[EMAIL PROTECTED]> wrote: >> From: Martin Marques >> I encountered a rare BUG in the way PG is logging. Let me first enlight > with some configuration I have and PG version: > > Perhaps I'm missing something but I think it's not a bug but a > configuration problem. > >> log_min_error_statement| panic > > If you set this one to error instead of panic, you will have your > failed statements logged. > >> log_statement | all > > This one only logs successful queries so it's normal you don't have > the statement in the log file if it fails. > > Regards, > > -- - Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática| '@' || 'unl.edu.ar'; Universidad Nacional| DBA, Programador, del Litoral | Administrador - ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] BUG in logs
I encountered a rare BUG in the way PG is logging. Let me first enlight with some configuration I have and PG version: prueba2=> SELECT version(); version PostgreSQL 8.1.0 on sparc-unknown-linux-gnu, compiled by GCC cc (GCC) 4.0.3 2005 (prerelease) (Debian 4.0.2-4) (1 row) prueba2=> select name, setting from pg_settings where name like 'log%'; name| setting +- log_connections| on log_destination| stderr log_disconnections | off log_duration | off log_error_verbosity| default log_executor_stats | off log_hostname | off log_line_prefix| <%t> log_min_duration_statement | -1 log_min_error_statement| panic log_min_messages | notice log_parser_stats | off log_planner_stats | off log_rotation_age | 1440 log_rotation_size | 10240 log_statement | all log_statement_stats| off log_truncate_on_rotation | off (18 rows) Now, when I do something like the sentence below, I get an error, which is OK: prueba2=> SELECT * FROM perfiles WHERE codigo = AND perfil = 'something here'; ERROR: error de sintaxis en o cerca de <> at character 39 LINE 1: SELECT * FROM perfiles WHERE codigo = AND perfil = 'somethin... But I should see in the logs the query and then the error, which is not what I'm getting at the momento (I only get the error, ad is shown below). <2006-04-11 16:31:03 ART>ERROR: error de sintaxis en o cerca de <> en car?cter 39 If anymore information is needed, let me know. -- - Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática| '@' || 'unl.edu.ar'; Universidad Nacional| DBA, Programador, del Litoral | Administrador - ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
