Re: [PATCH] SQL function to report log message

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: [PATCH] SQL function to report log message
Дата
Msg-id CAFj8pRBP3ScKPEJp6-z-fFqdAni9rn2o12GtA00JfsEXOe9w1A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PATCH] SQL function to report log message  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: [PATCH] SQL function to report log message  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers


2015-10-22 23:54 GMT+02:00 Jim Nasby <Jim.Nasby@bluetreble.com>:
On 10/22/15 4:42 PM, Pavel Stehule wrote:
the behave of pg_report_log should not be exactly same as RAISE
statement in PLpgSQL.

That makes no sense to me. Having different behaviors is just going to lead to confusion.

If this function will be exactly same, then it
lost a sense and anybody can use RAISE statement.

It prevents everyone from reinventing the 'create a function wrapper around RAISE' wheel that several people on this list alone have admitted to. I think there's plenty of value in that.

I have different opinion, I am sorry. The RAISE statement is differently designed with different possibility - the function is limited by using variadic function, and should not to have same behave as RAISE. And I don't like a idea to push RAISE to behave of variadic function.

Regards

Pavel


 

--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

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

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: Avoid full page images in streaming replication?
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Avoid full page images in streaming replication?