|From:||Pavlo Golub <pavlo(dot)golub(at)cybertec(dot)at>|
|To:||Daniel Verite <daniel(at)manitou-mail(dot)org>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org|
|Subject:||Re: BUG #16034: `\set ECHO all` doesn't work for \e command|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Wed, Oct 2, 2019 at 7:47 PM Daniel Verite <daniel(at)manitou-mail(dot)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
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
|Next Message||Tom Lane||2019-10-03 14:51:46||Re: BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql|
|Previous Message||PG Bug reporting form||2019-10-03 06:38:33||BUG #16035: STATEMENT_TIMEOUT not working when we have single quote usage inside CTE which is used in inner sql|