Skip site navigation (1) Skip section navigation (2)

Re: BUG #2180: log_statement=mod does not work

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Gilles <s_gilou(at)yahoo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2180: log_statement=mod does not work
Date: 2006-01-19 22:07:24
Message-ID: 20060119220724.GA15550@winnie.fuhr.org (view raw or flat)
Thread:
Lists: pgsql-bugs
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

In response to

pgsql-bugs by date

Next:From: Dave ByrneDate: 2006-01-19 22:13:16
Subject: BUG #2187: ERROR: buffer xxxxx is not owed by resource owner TopTransaction
Previous:From: Seneca CunninghamDate: 2006-01-19 22:03:18
Subject: Re: BUG #2168: 45.000.000 records too much?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group