| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | depesz(at)depesz(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: flood in logs |
| Date: | 2008-10-10 12:58:42 |
| Message-ID: | 23922.1223643522@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> 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".
Right, we don't bother to call GetCommandLogLevel if the setting is ALL
or NONE, so the oversight isn't exposed by default.
> so, for now i think it's better to set it to 'none' - and wait for
> new release with fix?
Either that or patch it locally.
I wonder if there are any other omissions in that function...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Serge Fonville | 2008-10-10 13:00:30 | Fwd: Socket error instead of Access denied |
| Previous Message | Serge Fonville | 2008-10-10 12:54:28 | Socket error instead of Access denied |