Re: [PROPOSAL] Client Log Output Filtering
От | David Steele |
---|---|
Тема | Re: [PROPOSAL] Client Log Output Filtering |
Дата | |
Msg-id | 56E17FEA.2030800@pgmasters.net обсуждение исходный текст |
Ответ на | Re: [PROPOSAL] Client Log Output Filtering (Petr Jelinek <petr@2ndquadrant.com>) |
Ответы |
Re: [PROPOSAL] Client Log Output Filtering
Re: [PROPOSAL] Client Log Output Filtering |
Список | pgsql-hackers |
On 3/9/16 7:37 PM, Petr Jelinek wrote: > On 03/02/16 05:02, Robert Haas wrote: >> On Mon, Feb 1, 2016 at 7:24 PM, David Steele <david@pgmasters.net> wrote: >>> >>> I have attached a patch that adds an ereport() macro to suppress client >>> output for a single report call (applies cleanly on 1d0c3b3). I'll also >>> move it to the next CF. >> >> I don't see any reason not to accept this. >> > > Yes, the idea seems sane. > > Looking at the code, this adds bool hide_from_client to edata which is > not initialized in errstart so that needs to be fixed. I figured this would take care of it: MemSet(edata, 0, sizeof(ErrorData)); Since I want hide_from_client to default to false. Am I missing something? -- -David david@pgmasters.net
В списке pgsql-hackers по дате отправления: