Re: flood in logs

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: flood in logs
Date: 2008-10-10 12:50:11
Message-ID: 20081010125011.GA21057@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Oct 10, 2008 at 08:42:02AM -0400, Tom Lane wrote:
> Mph, so it's an omission in the log_statement code. You must have
> log_statement set to mod or ddl on this machine.

yes. it's ddl. and on the machine that doesn't print the warning - it's
"none".

I also checked current (well, from 2 days ago) head - and the problem is
there as well.
so, for now i think it's better to set it to 'none' - and wait for
new release with fix?

best regards,

depesz

--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: depesz(at)depesz(dot)com / aim:depeszhdl / skype:depesz_hdl / gg:6749007

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Serge Fonville 2008-10-10 12:54:28 Socket error instead of Access denied
Previous Message Norberto Delle 2008-10-10 12:47:12 Idle in transaction connection