Hi All, On Tue, Nov 17, 2015 at 12:10 PM, Peter Eisentraut <pete...@gmx.net> wrote:
> 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. > > Sorry for being too late on this, as I have engaged into some other personal tasks. Could someone let me know, what else I need to do to get this patch completed. Any further suggestions on function name. If all OK with pg_log or someother, I would modify the patch, and will submit new one. Kindly let me know. Thanks in advance. -- Regards, Dinesh manojadinesh.blogspot.com
