Re: [PATCH] SQL function to report log message

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: [PATCH] SQL function to report log message
Дата
Msg-id CAFj8pRDaDeqM2PxGqJOxYNmmbtbzffUs+FoVmA93G_-r5x4SqQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] SQL function to report log message  (David Fetter <david@fetter.org>)
Список pgsql-hackers


2015-09-10 2:47 GMT+02:00 David Fetter <david@fetter.org>:
On Thu, Sep 10, 2015 at 01:32:10AM +0200, Andres Freund wrote:
> On 2015-09-09 18:27:51 -0400, Robert Haas wrote:
> > On Wed, Sep 9, 2015 at 11:37 AM, dinesh kumar <dineshkumar02@gmail.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?

+20 or so here, that being the number of times I recall offhand having
written the function.

I have same opinion - it is pretty often used function.

Pavel
 

Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Freeze avoidance of very large table.
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: proposal: function parse_ident