Thread: SQL Statement Missing From Log

SQL Statement Missing From Log

From
Bryce Nesbitt
Date:
Dear Helpful People,

I'm getting a bunch of:

2008-10-25 14:36:59 PDT ERROR:  syntax error at or near "SET" at character 9
2008-10-25 14:36:59 PDT ERROR:  syntax error at or near "fetch" at
character 9
2008-10-25 14:36:59 PDT ERROR:  current transaction is aborted, commands
ignored until end of transaction block

With no idea where the "SET" is coming from.   My logging configuration
is as follows.  What am I doing wrong?  How can I get the full failing
SQL statement?

# grep "log_" postgresql.conf  | grep -v "^#"
log_min_messages = notice               # =notice Values, in order of
decreasing detail:
log_error_verbosity = verbose           # =default terse, default, or
verbose messages
log_min_duration_statement = 250        # -1 is disabled, 0 logs all
statements
log_line_prefix = '%t '                 # Special values:
debug_pretty_print =on      # = off




Re: SQL Statement Missing From Log

From
Tom Lane
Date:
Bryce Nesbitt <bryce2@obviously.com> writes:
> I'm getting a bunch of:

> 2008-10-25 14:36:59 PDT ERROR:  syntax error at or near "SET" at character 9
> 2008-10-25 14:36:59 PDT ERROR:  syntax error at or near "fetch" at
> character 9
> 2008-10-25 14:36:59 PDT ERROR:  current transaction is aborted, commands
> ignored until end of transaction block

> With no idea where the "SET" is coming from.   My logging configuration
> is as follows.  What am I doing wrong?  How can I get the full failing
> SQL statement?

log_min_error_statement needs to be ERROR or less.
        regards, tom lane