Re: "unexpected EOF" messages

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: "unexpected EOF" messages
Дата
Msg-id CA+U5nMLvtKNgxAOZCq_Ph294Gggv2b5GoPwNU8=0PA1wP6QmBA@mail.gmail.com
обсуждение исходный текст
Ответ на "unexpected EOF" messages  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: "unexpected EOF" messages  (Magnus Hagander <magnus@hagander.net>)
Re: "unexpected EOF" messages  (Vik Reykja <vikreykja@gmail.com>)
Re: "unexpected EOF" messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Thu, May 3, 2012 at 1:26 PM, Magnus Hagander <magnus@hagander.net> wrote:
> I had a request from a customer asking if we could make a switch to
> specifically disable the "unexpected EOF" message that fills lots of
> peoples logs. Along the same way that we have a flag to turn off the
> "nonstandard use of string escapes" message that is another culprit
> (that's actually a much *worse* problem than just the unexpected EOF).
> The unexpected EOF message *does* indicate the client is doing
> something stupid, but it's not like it's an *actual problem* in pretty
> much every deployment out there...
>
> Would we consider adding such a switch (it should be easy enough to
> do), or do we want to push this off to the mythical "let's improve the
> logging subsystem" project that might eventually materialize if we're
> lucky? Meaning - would people object to such a switch?

Yes, if the new parameter allows a generic filter on multiple
user-specified message types.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: "unexpected EOF" messages
Следующее
От: Magnus Hagander
Дата:
Сообщение: ALTER DATABASE and datallowconn