| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | dinesh kumar <dineshkumar02(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(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 20:03:33 |
| Message-ID: | 56294115.8080500@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/22/15 3:20 AM, dinesh kumar wrote:
> postgres=# SELECT pg_report_log('INFO', 'NULL', false, NULL, NULL);
> INFO: NULL
>
> postgres=# SELECT pg_report_log('INFO', 'NULL', false, 'NULL', 'NULL');
> INFO: NULL
> DETAIL: NULL /-- Are you suggesting to change this behaviour/
> HINT: NULL
These look wrong to me.
I'd throw an error if a null message is passed.
(Not particularly in favor of this patch, but just saying ...)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-10-22 20:27:33 | Re: Dangling Client Backend Process |
| Previous Message | Robert Haas | 2015-10-22 20:01:21 | Re: make Gather node projection-capable |