| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] Client Log Output Filtering |
| Date: | 2016-03-29 17:08:28 |
| Message-ID: | 20160329170828.GC25907@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-03-29 12:58:22 -0400, Tom Lane wrote:
> Looking back at the earlier thread Andres mentioned, I see that he was
> specifically on about being able to do ereport(ERROR | LOG_NO_CLIENT),
> which I've got a problem with because of the point about not breaking
> wire-protocol expectations.
Yes. The reason for doing it in that case is that we weren't allowed to
send errors to the client in that specific case - by the protocol state.
There's a number of cases during early startup/auth where we really
don't want client to get messages.
> and it doesn't look like he thought about the elevel-comparisons
> issue either.
Nope, I didn't. That's a long while ago ;)
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-03-29 17:09:05 | Re: Move PinBuffer and UnpinBuffer to atomics |
| Previous Message | Robert Haas | 2016-03-29 17:05:54 | Re: [PROPOSAL] Client Log Output Filtering |