From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: One-shot expanded output in psql using \G |
Date: | 2017-01-27 15:05:29 |
Message-ID: | 20170127150529.GA26422@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 27, 2017 at 02:27:37PM +0100, Christoph Berg wrote:
> I frequently find myself in the situation that I want the "\x"
> expanded output mode activated just for one query. There's little
> wrong with typing "\x" and re-executing the query in that case, but
> then I'm always annoyed that the expanded output is still active for
> the next query after that.
+1
Your situation is familiar to me, and likely common among heavy users
of psql.
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-01-27 15:08:07 | Re: BUG: pg_stat_statements query normalization issues with combined queries |
Previous Message | Tom Lane | 2017-01-27 15:03:07 | Re: BUG: pg_stat_statements query normalization issues with combined queries |