Hi, While log_statements logs parameter values with the logged queries, I cannot see parameter values logged for erronous queries and queries catched by log_min_duration_statements.
Here are our logging settings: # grep ^log postgresql.conf logging_collector = on # Enable capturing of stderr and csvlog log_directory = '/srv/pg/pg_log' # directory where log files are written, log_filename = '%Y-%m-%d_%H%M%S.log' # log file name pattern, log_rotation_age = 7d # Automatic rotation of logfiles will log_rotation_size = 0MB # Automatic rotation of logfiles will log_min_duration_statement = 1000 # -1 is disabled, 0 logs all statements log_line_prefix = '%d %u %m ' # special values: For instance, consider below log snippets. eray_1_5_1_0 emove 2008-06-19 10:19:50.124 EEST ERROR: function isnull(integer, integer) does not exist at character 195 eray_1_5_1_0 emove 2008-06-19 10:19:50.124 EEST HINT: No function matches the given name and argument types. You might need to add explicit type casts. eray_1_5_1_0 emove 2008-06-19 10:19:50.124 EEST STATEMENT: SELECT * FROM mugroup g WHERE g.groupid IN ((... user id=$1) UNION (SELECT ...)) test_1_5_0_0 emove 2008-05-15 15:07:08.631 EEST LOG: duration: 68544.986 ms parse <unnamed>: insert into interprettimelog (...) values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16) Is this something expected? What might I be missing? How can I make PostgreSQL log parameter values also? Regards. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
