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

From Robert Haas
Subject Re: [PATCH] SQL function to report log message
Date
Msg-id CA+TgmoYt_V9zHEA9K7nSZTdPr_+xAe1QEC3D+QWFNWuFkF1baQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] SQL function to report log message  (dinesh kumar <dineshkumar02@gmail.com>)
Responses Re: [PATCH] SQL function to report log message  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: [PATCH] SQL function to report log message  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Wed, Sep 9, 2015 at 11:37 AM, dinesh kumar <dineshkumar02@gmail.com> wrote:
> I am admitting here that, I don’t know the real use case behind this
> proposal in our TODO list. I thought, having ereport wrapper at SQL level,
> gives a default debugging behavior for the end users, and this is the only
> real use case I see.
>
...
> Sure, it’s a clear fact that, we can implement this function with RAISE
> statements.

Given that, I suggest we just forget the whole thing.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: Modernizing contrib/tablefunc
Next
From: Robert Haas
Date:
Subject: Re: Parallel Seq Scan