Re: proposal: psql command \graw

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: psql command \graw
Date: 2017-11-10 15:38:57
Message-ID: alpine.DEB.2.20.1711101630060.668@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello,

>> Maybe I'm missing something, but it looks that it could be made to work
>> without adding another boolean.
>
> The tuples only cannot be disabled, because then other parts print number
> of rows
>
> postgres=# \pset format unaligned
> Output format is unaligned.
>
> postgres=# select 10 as a, 20 as b;
> a|b
> 10|20
> (1 row) ----<<<<<

Argh. Too bad.

I'm not at ease with having two bools which nearly mean the opposite one
of the other but not exactly... however I'm not sure that there is a
simpler way out of this, some exception handling is needed one way or the
other, either within the header or within the footer... Maybe the whole
topt logic should be reviewed, but that is not the point of this patch.

So I switched the patch to "ready for committer".

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2017-11-10 15:46:11 pg_upgrade to clusters with a different WAL segment size
Previous Message Tom Lane 2017-11-10 15:34:48 Re: Simplify ACL handling for large objects and removal of superuser() checks