Re: [PROPOSAL] Client Log Output Filtering

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [PROPOSAL] Client Log Output Filtering
Дата
Msg-id 9677.1459783275@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [PROPOSAL] Client Log Output Filtering  (David Steele <david@pgmasters.net>)
Ответы Re: [PROPOSAL] Client Log Output Filtering  (David Steele <david@pgmasters.net>)
Список pgsql-hackers
David Steele <david@pgmasters.net> writes:
> On 3/29/16 12:58 PM, Tom Lane wrote:
>> ...  Basically,
>> my point is that LOG_ONLY achieves 95% of the benefit for probably
>> 0.01% of the work.

> Attached is a patch that re-purposes COMMERROR as LOG_SERVER_ONLY.  I 
> went ahead and replaced all instances of COMMERROR with LOG_SERVER_ONLY.

Uh, what?  COMMERROR is a distinct concept in my opinion.  It might happen
to share the same implementation today, but that doesn't make it the
same thing.

I had in mind a patch that simply added LOG_SERVER_ONLY as another define
and did whatever seemed appropriate documentation-wise.  I see no reason
to touch the places that are currently dealing with client communication
failures.
        regards, tom lane



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

Предыдущее
От: Aleksander Alekseev
Дата:
Сообщение: Re: Tiny patch: sigmask.diff
Следующее
От: Tom Lane
Дата:
Сообщение: Re: postgres_fdw : altering foreign table not invalidating prepare statement execution plan.