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

From Peter Eisentraut
Subject Re: [PATCH] SQL function to report log message
Date
Msg-id 564B89C8.8060207@gmx.net
Whole thread Raw
In response to Re: [PATCH] SQL function to report log message  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [PATCH] SQL function to report log message  (dinesh kumar <dineshkumar02@gmail.com>)
List pgsql-hackers
On 11/17/15 2:16 AM, Jim Nasby wrote:
> On 11/15/15 10:56 PM, dinesh kumar wrote:
>> So, shall we make this pg_report_log TO pg_write_log OR pg_ereport OR
>> <SOME OTHER GOOD SUGGESTIONS> from you.
> 
> Why not pg_raise to mirror plpgsql? (The function does have the same
> semantics, right? It's not doing something like only sending to the log
> and not the client?)

I think the "raise" terminology is specific to plpgsql, as it actually
raises an exception in that language.




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [DESIGN] ParallelAppend
Next
From: Peter Eisentraut
Date:
Subject: Re: Patch: Implement failover on libpq connect level.