From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, dinesh kumar <dineshkumar02(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, 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-18 19:20:41 |
Message-ID: | CA+TgmoYWehEUF6cQmG8Tme7J+yunOxNSLhDxOMWYoasjYhPCGA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 16, 2015 at 5:41 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 11/16/15 5:10 PM, Tom Lane wrote:
>> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>>> On 11/15/15 9:50 PM, Craig Ringer wrote:
>>>> I'd prefer to omit fields if explicitly assigned to NULL. You can always
>>>> use coalesce if you want the string 'NULL'; I agree with others here
>>>> that the vast majority of users will want the field just omitted.
>>
>>> I think the problem was that you can't omit the primary message.
>>
>> If you ask me, that would be a feature not a bug.
>
> Right.
>
> Frankly, I have lost track of what the problem here is.
I am still of the opinion that this patch is a solution in search of a problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-11-18 19:28:35 | Re: proposal: multiple psql option -c |
Previous Message | Jeff Janes | 2015-11-18 19:18:22 | Re: Freeze avoidance of very large table. |