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 56204923.4080508@BlueTreble.com
Whole thread Raw
In response to Re: [PATCH] SQL function to report log message  (Andres Freund <andres@anarazel.de>)
Responses Re: [PATCH] SQL function to report log message  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On 9/10/15 10:56 AM, Andres Freund wrote:
>> >The only complaint I've seen in this thread that seems like a valid
>> >deficiency is that RAISE can't deal with treating the error severity level
>> >as a variable.  But surely we should address that as a new RAISE feature,
>> >not by inventing a SQL wrapper that will need to reproduce every existing
>> >RAISE feature before it can think about solving anything new.
> That seems like something independently useful.

If we're up for that the other thing I'd add is having raise ignore 
anything supplied by USING that's NULL, instead of treating it as an 
error. That would make it very easy to create a wrapper function that 
exposes the full capabilities of RAISE.
-- 
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: Improve the concurency of vacuum full table and select statement on the same relation
Next
From: Jim Nasby
Date:
Subject: Re: pg_dump LOCK TABLE ONLY question