From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
Cc: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Extensions, this time with a patch |
Date: | 2010-10-20 13:44:16 |
Message-ID: | AANLkTimPgp5LWAzqpcZ9hV3xx7aeBo1L6HobXeM0UUtU@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 20, 2010 at 9:33 AM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I would vote for overriding client_min_messages but not log_min_messages.
>
> Well it defaults to WARNING so I see your point. Then again, we're
> talking about hundreds of lines (3197 lines of isn, 531 lines for
> hstore) of output per message, containing a script that you're not
> maintaining. Do we really want that amount of extra logging?
Well, my thought was that it makes sense to override the user's
logging preferences because, after all, if they wanted the extra
logging, they could run the script by hand. But what gets logged to
the system log is server policy, not user preference, and I'm
reluctant to think we should second-guess whatever the admin has
configured.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-10-20 14:00:40 | Re: leaky views, yet again |
Previous Message | Dimitri Fontaine | 2010-10-20 13:33:10 | Re: Extensions, this time with a patch |