From: | Jon Jensen <jon(at)endpoint(dot)com> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: \x and slash commands |
Date: | 2005-06-10 16:42:57 |
Message-ID: | Pine.LNX.4.63.0506101041370.11665@ynfu.ovalna.fjrygre.arg |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 10 Jun 2005, Neil Conway wrote:
> Someone commented to me recently that they usually use psql's \x "expanded
> output" mode, but find that it produces pretty illegible results for psql
> slash commands such as \d. I can't really see a reason you would _want_
> "expanded output" mode for the result sets of psql slash commands. Would
> anyone object to changing \x to not affect that way that the result sets of
> slash commands are printed?
I would very much like to see that behavior changed, but if there are
people who like it the way it is, maybe we can have a \X command that uses
expanded mode only for non-slash output.
What do others think about this?
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-10 16:46:32 | Re: Gist Recovery testing |
Previous Message | Bruce Momjian | 2005-06-10 16:33:32 | Re: User Quota Implementation |