Re: [PATCH] SQL function to report log message - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [PATCH] SQL function to report log message
Date
Msg-id CAMsr+YEN+uCSTqB82y21wMDxdKKGC1Om4Cwdc02Vg7ayZHMAPQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] SQL function to report log message  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCH] SQL function to report log message  (Kevin Grittner <kgrittn@ymail.com>)
Re: [PATCH] SQL function to report log message  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On 16 November 2015 at 09:50, Peter Eisentraut <peter_e@gmx.net> wrote:

I haven't seen this discussed before, but I don't find the name
pg_report_log particularly good.  Why not jut pg_log?


Sounds like a better name to me. 'report' is noise that adds nothing useful.

I'd like to have this functionality.

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.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Haribabu Kommi
Date:
Subject: Re: [PATCH] Skip ALTER x SET SCHEMA if the schema didn't change
Next
From: Peter Eisentraut
Date:
Subject: Re: pam auth - add rhost item