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

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Pavlo Golub" <pavlo(dot)golub(at)cybertec(dot)at>
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
Date: 2019-10-02 17:47:49
Message-ID: b1ab70c7-3603-44fc-b5e3-a5b412fab941@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Raymond 2019-10-02 18:36:33 RE: BUG #16031: Group by returns duplicate groups
Previous Message Tom Lane 2019-10-02 16:51:47 Re: BUG #16034: `\set ECHO all` doesn't work for \e command