Skip site navigation (1)
Skip section navigation (2)
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?
Peripheral Links
Header And Logo
|
Site Navigation
psql: \x and slash commands
- From: Neil Conway <neilc(at)samurai(dot)com>
- To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
- Subject: psql: \x and slash commands
- Date: Fri, 10 Jun 2005 11:53:22 +1000
- Message-id: <42A8F292(dot)8060206(at)samurai(dot)com>
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?
-Neil
- Follow-Ups:
- Re: psql: \x and slash commands
- From: Jon Jensen
- Re: psql: \x and slash commands
- From: Christopher Kings-Lynne
- Re: psql: \x and slash commands
- Prev by Date: Re: Bug in pg_restore ... ?
- Next by Date: Re: psql: \x and slash commands
- Previous by thread: Workaround for cross-compilation
- Next by thread: Re: psql: \x and slash commands
- Indexes: