Re: [PROPOSAL] Client Log Output Filtering

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [PROPOSAL] Client Log Output Filtering
Дата
Msg-id 3853.1457626026@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [PROPOSAL] Client Log Output Filtering  (Petr Jelinek <petr@2ndquadrant.com>)
Ответы Re: [PROPOSAL] Client Log Output Filtering  (Petr Jelinek <petr@2ndquadrant.com>)
Re: [PROPOSAL] Client Log Output Filtering  (David Steele <david@pgmasters.net>)
Список pgsql-hackers
Petr Jelinek <petr@2ndquadrant.com> writes:
> The comment above errhidefromclient says "Only log levels below ERROR 
> can be hidden from the client." but use of the errhidefromclient(true) 
> actually does hide the error message from client, client just gets 
> failed query without any message when used with ERROR level.

Um.  That seems pretty broken --- I think it's a violation of the wire
protocol spec.

I notice though that we allow client_min_messages to be set to FATAL,
which would be a different way of violating the protocol.  Maybe we
should reduce the max setting of that to ERROR?

libpq/psql seem to more or less survive this situation:

regression=# set client_min_messages to fatal;
SET
regression=# select 2/0;
regression=# select 1;?column? 
----------       1
(1 row)

but it doesn't really seem like a great idea.
        regards, tom lane



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

Предыдущее
От: Dmitrii Golub
Дата:
Сообщение: Re: unexpected result from to_tsvector
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Explain [Analyze] produces parallel scan for select Into table statements.