http://www.postgresql.org/docs/8.4/interactive/runtime-config-logging.html#GUC-LOG-STATEMENT
[...]
Valid values are none, ddl, mod, and all.
regards
andreas
On 08/27/2010 03:01 PM, Richard Harley wrote:
Won't log state = all catch everything?
Richard
On 27/08/10 10:39, Mike Christense
Won't log state = all catch everything?
Richard
On 27/08/10 10:39, Mike Christensen wrote:
Hi all -
I've noticed my log files for Postgres are getting way too big, since
every single SQL statement being run ends up in the log. However,
nothing I change in postgresql.conf seems to make a bit
Yup, someone emailed me privately - this fixed the problem.. Thanks!
On Fri, Aug 27, 2010 at 2:55 AM, Thomas Kellerer wrote:
> Mike Christensen, 27.08.2010 11:39:
>>
>> Hi all -
>>
>> I've noticed my log files for Postgres are getting way too big, since
>> every single SQL statement being run en
Mike Christensen, 27.08.2010 11:39:
Hi all -
I've noticed my log files for Postgres are getting way too big, since
every single SQL statement being run ends up in the log. However,
nothing I change in postgresql.conf seems to make a bit of
difference.. I've tried restarting postgres, deleting
Hi all -
I've noticed my log files for Postgres are getting way too big, since
every single SQL statement being run ends up in the log. However,
nothing I change in postgresql.conf seems to make a bit of
difference.. I've tried restarting postgres, deleting all the
existing logs, etc. No matter
