From: | "Erik Rijkers" <er(at)xs4all(dot)nl> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: some psql table output flaws |
Date: | 2013-02-01 21:03:32 |
Message-ID: | b529ca1fd8f322bdce38d2db0f0f946f.squirrel@webmail.xs4all.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, February 1, 2013 21:22, Peter Eisentraut wrote:
> I have encountered two unrelated flaws in the psql table output.
>
> First, when using unaligned vertical mode (\a \x on), there is always an
> empty line after the last record. This also means that an empty result
> set prints an empty line, instead of nothing.
>
> Second, when using aligned vertical mode (\x on), an empty result set
> prints "(No rows)". That's fine, but there is no way to turn this off.
> I intuitively attempted to use \t (tuples only), but that had no
> effect. \t doesn't really have a meaning in vertical mode, because the
> field names are always printed, but I think it could/should have the
> effect of shutting off footer lines.
>
> Patch for both issues attached.
>
+1
I'd be very glad not to have to 'grep -v' this stuff away all the time
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-02-01 21:15:45 | Re: GetOldestXmin going backwards is dangerous after all |
Previous Message | Peter Eisentraut | 2013-02-01 20:22:33 | some psql table output flaws |