On Jan 22, 2010, at 2:55 AM, Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>
>>> Jim Nasby wrote:
>>>
>>>> Why does warn; in plperl log as NOTICE in Postgres?
>>>>
>>
>>
>>> Where would you like the warning to go? This has been this way for nearly 5 years, it's not new (and before that
thewarning didn't go anywhere).
>>>
>>
>> I think he's suggesting that it ought to translate as elog(WARNING)
>> not elog(NOTICE).
>>
>>
>>
>
> *shrug* I don't have a strong opinion about it, and it's pretty easy to change, if there's a consensus we should. I
havecertainly found over the years that perl warnings from some modules can be annoyingly verbose, which is probably
whythe original patch didn't make them have a higher level in Postgres. If this were a big issue we'd have surely heard
aboutit before now - there are plenty of plperl users out there.
I think elog(WARNING) is less surprising for the end-user, unless there's an objection strong enough to include it into
thedocumentation :)
--
Alexey Klyukin http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc