Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #16034: `\set ECHO all` doesn't work for \e command - Mailing list pgsql-bugs

From Pavlo Golub
Subject Re: BUG #16034: `\set ECHO all` doesn't work for \e command
Date
Msg-id CAK7ymcKaS33GBUexEJqiWO1=7x0spUwpH01vNpb6iTOF+Hjg-w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16034: `\set ECHO all` doesn't work for \e command  ("Daniel Verite" <daniel@manitou-mail.org>)
Responses Re: BUG #16034: `\set ECHO all` doesn't work for \e command
List pgsql-bugs
Tree view 
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 by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql
Next
From: Tom Lane
Date:
Subject: Re: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql