Re: [PATCH] SQL function to report log message

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: dinesh kumar <dineshkumar02(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, 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-09-09 23:32:10
Message-ID: 20150909233210.GD12694@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-09-09 18:27:51 -0400, Robert Haas wrote:
> On Wed, Sep 9, 2015 at 11:37 AM, dinesh kumar <dineshkumar02(at)gmail(dot)com> wrote:
> > 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.

I'm not convinced. Sure, it's easy, but I by now have written the
respective function dozens of times. Why should we force that on
everyone?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Charles Sheridan 2015-09-09 23:53:31 Do Layered Views/Relations Preserve Sort Order ?
Previous Message Jim Nasby 2015-09-09 23:19:03 Re: [PATCH] SQL function to report log message