From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql \d sequence display |
Date: | 2017-09-29 17:50:46 |
Message-ID: | 8b8be2a1-d4aa-31fc-2dbb-dd409502d4e9@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/25/17 13:53, Fabien COELHO wrote:
> \d+ does not show more.
>
> Maybe Type, Min, Max, Inc & Cycles are enough for \d?
That seems kind of arbitrary. Start and Cache are just as relevant.
> The next/future or last/previous value is not shown. If one could be
> available it would be nice to have?
You can get those from the sequence. Running \d on a table doesn't show
the table data either. So I think this is a valid distinction.
> Maybe some names are a little large, eg "Increment" could be "Inc.".
> The value is nearly always 1?
Yeah, but then that would look weird if only one heading were
abbreviated. The total display width is good, so we don't need to
squeeze it too hard.
> Not sure why it is "Cycles" (plural) instead of "Cycle".
This is meant to be a verb, as in "does it cycle?". I have changed it
to "Cycles?" to match other similar headings.
> I do not understand why some queries have "... \n" "... \n" and others
> have "\n ..." "\n ...". I would suggest to homogeneize around the former,
> because "\nFROM ..." is less readable.
Yeah that is a bit ugly, but I have just moved existing code around.
I have now committed my patch with minor adjustments, so we have
something working for PG10.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-09-29 17:54:02 | Re: A design for amcheck heapam verification |
Previous Message | Tom Lane | 2017-09-29 17:47:59 | Re: alter server for foreign table |