From: | dinesh kumar <dineshkumar02(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] SQL function to report log message |
Date: | 2015-11-23 17:46:46 |
Message-ID: | CALnrH7qQWnenN6L9eSqdEWBUa5Yz9+M40NF9gS8yMG7sOSSNOw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi All,
On Tue, Nov 17, 2015 at 12:10 PM, Peter Eisentraut <peter_e(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2015-11-23 18:41:42 | New email address |
Previous Message | Robert Haas | 2015-11-23 17:43:56 | Re: [PROPOSAL] VACUUM Progress Checker. |