Re: [PATCH] SQL function to report log message - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [PATCH] SQL function to report log message
Date
Msg-id CAFj8pRAWbU+8h=oc1kjqjOkgFuhvgR2oCj8COL+q3E1zrTocwA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] SQL function to report log message  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] SQL function to report log message  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers


2015-10-20 16:50 GMT+02:00 Robert Haas <robertmhaas@gmail.com>:
On Mon, Oct 19, 2015 at 7:59 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> I fail to see how doing
>
> HINT: NULL
>
> is much better than just not raising a HINT at all...

I'm not a huge fan of this patch, as previously noted, but I certainly
agree that if we're going to do it, we should ignore a null argument,
not print out the word "NULL".  Who would ever want that behavior?

Probably it was my request. I don't like to using NULL as value, that should be ignored. The "hint" is clean, there NULL can be ignored, but what about DETAIL or MESSAGE?

I am strong in my opinion about PLpgSQL RAISE statement behave, but on second hand, proposed function should not be 100% same as RAISE stmt. More we can simply add a parameter like "ignore_nulls"

Regards

Pavel

 

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: ROWS FROM(): A Foolish (In)Consistency?
Next
From: Robert Haas
Date:
Subject: Re: Typos in plannodes.h