BUG #2180: log_statement=mod does not work

Started by Gillesabout 20 years ago3 messagesbugs
Jump to latest
#1Gilles
s_gilou@yahoo.com

The following bug has been logged online:

Bug reference: 2180
Logged by: Gilles
Email address: s_gilou@yahoo.com
PostgreSQL version: 8.1.0
Operating system: Linux RedHat ES3
Description: log_statement=mod does not work
Details:

When I configure in the file postgresql.conf:
log_statement=mod
I don't have the update, delete, insert queries logged like it says in the
documentation :
http://www.postgresql.org/docs/8.1/interactive/runtime-config-logging.html

Could you tell me, what I need to do to get these queries logged?

Thanks
Gilles

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Gilles (#1)
Re: BUG #2180: log_statement=mod does not work

"Gilles" <s_gilou@yahoo.com> writes:

When I configure in the file postgresql.conf:
log_statement=mod
I don't have the update, delete, insert queries logged like it says in the
documentation :
http://www.postgresql.org/docs/8.1/interactive/runtime-config-logging.html

Did you remember to do "pg_ctl reload" (or kill -HUP the postmaster)
after changing the config file? Perhaps you neglected to remove the #
comment marker from that line in the file?

regards, tom lane

#3Michael Fuhr
mike@fuhr.org
In reply to: Gilles (#1)
Re: BUG #2180: log_statement=mod does not work

On Wed, Jan 18, 2006 at 03:38:17PM +0000, Gilles wrote:

When I configure in the file postgresql.conf:
log_statement=mod
I don't have the update, delete, insert queries logged like it says in the
documentation :
http://www.postgresql.org/docs/8.1/interactive/runtime-config-logging.html

Could you tell me, what I need to do to get these queries logged?

Works here. Did you restart or reload the server after making the
change? Are you sure you changed the right postgresql.conf (this can
be a problem if you have multiple versions of PostgreSQL installed)?
What does "SHOW log_statement" show? Are you sure you're looking in
the right log file? Do you see other log entries?

--
Michael Fuhr