Alternate Output Format For Psql


Answer :

I just needed to spend more time staring at the documentation. This command:

\x on

will do exactly what I wanted. Here is some sample output:

select * from dda where u_id=24 and dda_is_deleted='f'; -[ RECORD 1 ]------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- dda_id             | 1121 u_id               | 24 ab_id              | 10304 dda_type           | CHECKING dda_status         | PENDING_VERIFICATION dda_is_deleted     | f dda_verify_op_id   | 44938 version            | 2 created            | 2012-03-06 21:37:50.585845 modified           | 2012-03-06 21:37:50.593425 c_id               |  dda_nickname       |  dda_account_name   |  cu_id              | 1 abd_id             |

(New) Expanded Auto Mode: \x auto

New for Postgresql 9.2; PSQL automatically fits records to the width of the screen. previously you only had expanded mode on or off and had to switch between the modes as necessary.

  • If the record can fit into the width of the screen; psql uses normal formatting.
  • If the record can not fit into the width of the screen; psql uses expanded mode.

To get this use: \x auto

Postgresql 9.5 Documentation on PSQL command.

Wide screen, normal formatting:

 id | time  |       humanize_time             | value  ----+-------+---------------------------------+-------   1 | 09:30 |  Early Morning - (9.30 am)      |   570   2 | 11:30 |  Late Morning - (11.30 am)      |   690   3 | 13:30 |  Early Afternoon - (1.30pm)     |   810   4 | 15:30 |  Late Afternoon - (3.30 pm)     |   930 (4 rows)

Narrow screen, expanded formatting:

-[ RECORD 1 ]-+--------------------------- id            | 1 time          | 09:30 humanize_time | Early Morning - (9.30 am) value         | 570 -[ RECORD 2 ]-+--------------------------- id            | 2 time          | 11:30 humanize_time | Late Morning - (11.30 am) value         | 690 -[ RECORD 3 ]-+--------------------------- id            | 3 time          | 13:30 humanize_time | Early Afternoon - (1.30pm) value         | 810 -[ RECORD 4 ]-+--------------------------- id            | 4 time          | 15:30 humanize_time | Late Afternoon - (3.30 pm) value         | 930

How to start psql with \x auto?

Configure \x auto command on startup by adding it to .psqlrc in your home folder and restarting psql. Look under 'Files' section in the psql doc for more info.

~/.psqlrc

\x auto

You have so many choices, how could you be confused :-)? The main controls are: 

# \pset format # \H # \x # \pset pager off

Each has options and interactions with the others. The most automatic options are:

# \x off;\pset format wrapped # \x auto

The newer "\x auto" option switches to line-by-line display only "if needed".

-[ RECORD 1 ]--------------- id          | 6 description | This is a gallery of oilve oil brands. authority   | I love olive oil, and wanted to create a place for reviews and comments on various types. -[ RECORD 2 ]--------------- id          | 19 description | XXX Test A  authority   | Testing

The older "\pset format wrapped" is similar in that it tries to fit the data neatly on screen, but falls back to unaligned if the headers won't fit. Here's an example of wrapped: 

 id |          description           |            authority             ----+--------------------------------+---------------------------------   6 | This is a gallery of oilve     | I love olive oil, and wanted to     ; oil brands.                    ;  create a place for reviews and     ;                                ;  comments on various types.  19 | Test Test A                    | Testing

Comments

Post a Comment

Popular posts from this blog

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more