| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | dinesh kumar <dineshkumar02(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-10-22 21:54:13 |
| Message-ID: | 56295B05.1010807@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2015-10-22 21:56:00 | Re: [PATCH] SQL function to report log message |
| Previous Message | Jim Nasby | 2015-10-22 21:51:04 | Re: Change behavior of (m)xid_age |