public inbox for [email protected]
help / color / mirror / Atom feedSubject: [Pljava-dev] pljava error logging levels
Date: Mon, 26 Jul 2010 14:08:34 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
Well the original question I asked was "Why does PL/Java try to filter log levels at all?". If we simply disabled the log filtering from PL/Java and let the log filtering happen naturally in Postgres then all of these problems just go away.
This could be accomplished using the attached patch.
Alternatively, significant improvement could be made by at least setting the log level correctly at init time by checking both log_min_messages AND client_min_messages and setting the log level to whichever is FINER grained logging. But since this still doesn't address changes to the GUCs over time it seems like a less desirable approach.
Regards,
Caleb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logHandler.patch
Type: application/octet-stream
Size: 4589 bytes
Desc: logHandler.patch
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20100726/ada19b3b/attachment.obj;
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001..txt
URL: <http://lists.pgfoundry.org/pipermail/pljava-dev/attachments/20100726/ada19b3b/attachment.txt;
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Subject: Re: [Pljava-dev] pljava error logging levels
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox