-----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 modules can be annoyingly > verbose, which is probably why the original patch didn't make them have > a higher level in Postgres. If this were a big issue we'd have surely > heard about it before now - there are plenty of plperl users out there. As a heavy user of Pl/Perl[U], this behavior has always surprised me, but never enough to bother complaining about it. However, count me as a +1 to make warn == elog(WARNING) - -- Greg Sabino Mullane g...@turnstep.com End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201001220941 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAktZuUEACgkQvJuQZxSWSsji4gCgwR8UEE4CimL8tAKnu0ZU+y+w nxkAn3MCOVCGr6BuCiRcjxrQ2/KCe/Bn =5Ukn -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
