Re: [PROPOSAL] Client Log Output Filtering
От | David Steele |
---|---|
Тема | Re: [PROPOSAL] Client Log Output Filtering |
Дата | |
Msg-id | 57028577.1030308@pgmasters.net обсуждение исходный текст |
Ответ на | Re: [PROPOSAL] Client Log Output Filtering (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [PROPOSAL] Client Log Output Filtering
|
Список | pgsql-hackers |
Hi Tom, On 3/29/16 12:58 PM, Tom Lane wrote: > Oh, I agree that there's a compelling use-case for LOG | > ERR_HIDE_FROM_CLIENT. I'm less certain that there's a use-case > for supporting such a flag across all elevels that is strong enough > to justify all the work we'd have to do to make it happen. 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. I left the COMMERROR #define but it is no longer used by any server, client, or included contrib code (I also noted that it was DEPRECATED in the comment). I'll leave it up to the committer to remove if deemed appropriate. I realize there's no agreement on how this should work ideally, but this patch answers the current need without introducing anything new and shouldn't cause regressions. It does address confusion that would arise from using COMMERROR in ereports that clearly are not. Thanks, -- -David david@pgmasters.net
Вложения
В списке pgsql-hackers по дате отправления: