Skip site navigation (1) Skip section navigation (2)

Re: VIP: new format for psql - shell - simple using psql in shell

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: VIP: new format for psql - shell - simple using psql in shell
Date: 2012-05-26 15:58:26
Message-ID: 20120526155826.GC23645@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, May 26, 2012 at 05:39:23PM +0200, Pavel Stehule wrote:
> Hello
> 
> I proposed new psql's format "shell". This format is optimized for
> processing returned result in shell:
> 
> 
> postgres=# select * from foo;
>       a       | b  |     c
> --------------+----+------------
>  Hello, World | 10 | 2012-05-26
>  Ahoj, Svete  | 20 | 2012-06-15
> (2 rows)
> 
> postgres=# \pset format shell
> Output format is shell.
> postgres=# select * from foo;
> a b c
> Hello,\ World 10 2012-05-26
> Ahoj,\ Svete 20 2012-06-15
> 
> postgres=# \x
> Expanded display is on.
> postgres=# select * from foo;
> ( c l )
> ( [a]=Hello,\ World [b]=10 [c]=2012-05-26 )
> ( [a]=Ahoj,\ Svete [b]=20 [c]=2012-06-15 )
...
> ) | while read dbname owner encoding collate ctype priv;

I am unclear exactly how this relates to shells.  Do shells read this
via read?  I am unclear that would actually work.  What do the brackets
mean?  Does read process \space as a non-space?

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-05-26 16:17:04
Subject: Re: Backends stalled in 'startup' state: index corruption
Previous:From: Euler TaveiraDate: 2012-05-26 15:54:25
Subject: Re: No, pg_size_pretty(numeric) was not such a hot idea

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group