Re: BUG #16034: `\set ECHO all` doesn't work for \e command

Поиск
Список
Период
Сортировка
От Pavlo Golub
Тема Re: BUG #16034: `\set ECHO all` doesn't work for \e command
Дата
Msg-id CAK7ymcKaS33GBUexEJqiWO1=7x0spUwpH01vNpb6iTOF+Hjg-w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #16034: `\set ECHO all` doesn't work for \e command  ("Daniel Verite" <daniel@manitou-mail.org>)
Ответы Re: BUG #16034: `\set ECHO all` doesn't work for \e command  ("Daniel Verite" <daniel@manitou-mail.org>)
Список pgsql-bugs
Дерево обсуждения 
On Wed, Oct 2, 2019 at 7:47 PM Daniel Verite <daniel@manitou-mail.org> wrote:
>
>         Pavlo Golub wrote:
>
> > As you can see, you have no idea what the query was executed.
> > And sometimes you really want to know that, especially trying to analyze
> > query were executed during a session.
> > Agree, probably ECHO is not the best solution since it's intended not
> > for interactive mode.
>
> \set ECHO queries
> would display them including immediately after \e in an interactive
> session.

Oh, great! That works! Thanks! But why ECHO all doesn't? Should all
include queries by default?
>
>
> Best regards,
> --
> Daniel Vérité
> PostgreSQL-powered mailer: http://www.manitou-mail.org
> Twitter: @DanielVerite

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

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql