Re: warn in plperl logs as... NOTICE?? - Mailing list pgsql-hackers

From Alexey Klyukin
Subject Re: warn in plperl logs as... NOTICE??
Date
Msg-id 4B9EFA5A-A7AC-406F-8E16-BC429D99F717@waki.ru
Whole thread Raw
In response to Re: warn in plperl logs as... NOTICE??  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: warn in plperl logs as... NOTICE??  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Jan 22, 2010, at 4:38 PM, Robert Haas wrote:

> On Fri, Jan 22, 2010 at 9:13 AM, Alexey Klyukin <alexk@waki.ru> wrote:
>> I think elog(WARNING) is less surprising for the end-user, unless there's an objection strong enough to include it
intothe documentation :) 
>
> I think the main possible objection would what Simon just wrote on the
> other thread - that it's been this way for a while, and while someone
> might think that a different decision about how to handle it would
> have been better, there may be people counting on the current behavior
> who will have to spend time and perhaps money making changes if we
> change it.

Well, then we have to choose between a fixed number of unhappy users in the past and potentially increasing number of
unhappyusers in the future (if we admit the fact that this behavior is illogical).  IMO if something behaves
counterintuitivelyto most users the behavior should be at least documented, if not fixed.   

--
Alexey Klyukin                    http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc



pgsql-hackers by date:

Previous
From: Brendan Jurd
Date:
Subject: Re: 8.5 vs. 9.0, Postgres vs. PostgreSQL
Next
From: Peter Eisentraut
Date:
Subject: Re: plpythonu DO support (inline call handler)