Alexey Klyukin wrote:
On Jan 22, 2010, at 4:38 PM, Robert Haas wrote:
On Fri, Jan 22, 2010 at 9:13 AM, Alexey Klyukin wrote:
I think elog(WARNING) is less surprising for the end-user, unless there's an
objection strong enough to include it into the documentation :)
I think
On Jan 22, 2010, at 4:38 PM, Robert Haas wrote:
> On Fri, Jan 22, 2010 at 9:13 AM, Alexey Klyukin wrote:
>> I think elog(WARNING) is less surprising for the end-user, unless there's an
>> objection strong enough to include it into the documentation :)
>
> I think the main possible objection wo
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
>>> Why does warn; in plperl log as NOTICE in Postgres?
> *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 have certainly found over
> the years that perl warnings from some mo
On Fri, Jan 22, 2010 at 9:13 AM, Alexey Klyukin wrote:
> I think elog(WARNING) is less surprising for the end-user, unless there's an
> objection strong enough to include it into the documentation :)
I think the main possible objection would what Simon just wrote on the
other thread - that it's
On Jan 22, 2010, at 2:55 AM, Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>> Andrew Dunstan 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
>>>
On Thu, Jan 21, 2010 at 07:55:09PM -0500, Andrew Dunstan wrote:
> Tom Lane wrote:
> >Andrew Dunstan 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
On Jan 21, 2010, at 4:55 PM, Andrew Dunstan wrote:
> *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 have certainly found over the
> years that perl warnings from some modules can be annoyingly verbose, which
> is probably wh
Tom Lane wrote:
Andrew Dunstan 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 the warning didn't go
anywhere).
I think h
Andrew Dunstan 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 the warning didn't go
> anywhere).
I think he's suggesting that it ought to tran
Jim Nasby wrote:
Why does warn; in plperl log as NOTICE in Postgres?
On a related note, what's the logic behind perl DEBUG logging as DEBUG2 instead
of DEBUG1 or DEBUG5? Still seems kind of odd, but at least nowhere near as
surprising as warn becoming NOTICE...
Where would you like the
Why does warn; in plperl log as NOTICE in Postgres?
On a related note, what's the logic behind perl DEBUG logging as DEBUG2 instead
of DEBUG1 or DEBUG5? Still seems kind of odd, but at least nowhere near as
surprising as warn becoming NOTICE...
--
Jim C. Nasby, Database Architect
11 matches
Mail list logo
