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

From Jim Nasby
Subject Re: [PATCH] SQL function to report log message
Date
Msg-id 56295B05.1010807@BlueTreble.com
Whole thread Raw
In response to Re: [PATCH] SQL function to report log message  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [PATCH] SQL function to report log message  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On 10/22/15 4:42 PM, Pavel Stehule wrote:
> the behave of pg_report_log should not be exactly same as RAISE
> statement in PLpgSQL.

That makes no sense to me. Having different behaviors is just going to 
lead to confusion.

> If this function will be exactly same, then it
> lost a sense and anybody can use RAISE statement.

It prevents everyone from reinventing the 'create a function wrapper 
around RAISE' wheel that several people on this list alone have admitted 
to. I think there's plenty of value in that.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Change behavior of (m)xid_age
Next
From: Pavel Stehule
Date:
Subject: Re: [PATCH] SQL function to report log message