Re: psql \G command -- send query and output using extended format

From: Decibel! <decibel(at)decibel(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Dawid Kuroczko" <qnex42(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql \G command -- send query and output using extended format
Date: 2008-04-07 18:50:17
Message-ID: CA780414-017B-4CDC-B458-1FF0035CCCEA@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Apr 3, 2008, at 9:35 AM, Tom Lane wrote:
> "Dawid Kuroczko" <qnex42(at)gmail(dot)com> writes:
>> The idea of \G command is to perform the query, but with printing
>> query results using extended table output format.
>
> Seems a bit useless --- if you prefer \x format, wouldn't you
> prefer it
> all the time? Or at least often enough that the toggling command is
> fine? I'm dubious that this is worth eating up a command letter for.

I agree about not eating a letter, but...

I often find myself wanting to do stuff like tuple-only output for a
single query in scripts. It would be nice if there was a command
(\G ?) that would accept additional options for controlling output.
It should be possible to map the options to existing psql output
stuff, so that you could force any single command to output in any
format that you wanted it to.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-04-07 18:58:34 Re: File system snapshots for multiple file systems
Previous Message Bruce Momjian 2008-04-07 18:45:33 File system snapshots for multiple file systems

Browse pgsql-patches by date

  From Date Subject
Next Message Zoltan Boszormenyi 2008-04-07 19:37:40 Re: TRUNCATE TABLE with IDENTITY
Previous Message Zdenek Kotala 2008-04-07 18:37:44 Re: Headers dependencies cleanup