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

From Daniel Verite
Subject Re: BUG #16034: `\set ECHO all` doesn't work for \e command
Date
Msg-id b1ab70c7-3603-44fc-b5e3-a5b412fab941@manitou-mail.org
Whole thread Raw
In response to Re: BUG #16034: `\set ECHO all` doesn't work for \e command  (Pavlo Golub <pavlo.golub@cybertec.at>)
Responses Re: BUG #16034: `\set ECHO all` doesn't work for \e command
List 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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16034: `\set ECHO all` doesn't work for \e command
Next
From: David Raymond
Date:
Subject: RE: BUG #16031: Group by returns duplicate groups