From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: \x and slash commands |
Date: | 2005-06-13 17:48:04 |
Message-ID: | 200506131348.04665.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thursday 09 June 2005 22:03, Christopher Kings-Lynne 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 have complained about that a few times before, but for some
> unbeknownst reason people thought that having totally messed up table
> displays was a feature, not a bug :)
>
If have found that \x on and \df+ can often produce nice results (especially
with a lot of \n in the function definitions.) I'm more neutral toward other
other things (\d on a table is kind of ugly, but \dv isnt so bad), but
wouldn't want to have to choose which ones some people would like and which
ones they wouldn't
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2005-06-13 18:28:08 | Re: The Contrib Roundup (long) |
Previous Message | Andrew Dunstan | 2005-06-13 17:20:50 | Re: The Contrib Roundup (long) |