| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, decibel <decibel(at)decibel(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Ricardo Bessa <ricardobessa(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Show method of index |
| Date: | 2009-05-19 15:27:30 |
| Message-ID: | 14687.1242746850@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On May 19, 2009, at 10:02 AM, Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>
> wrote:
>> One advantage of the current arrangement is that the constraints and
>> triggers are almost (though not quite) in the same form as the
>> command to create them. It would be sad to lose that competely.
> Agreed.
+1 --- I *very* often find myself copying-and-pasting from \d output,
and the proposed tabular format would be a huge step backwards for
that. Personally I kinda wish that the column display were closer
to what CREATE TABLE wants ...
> What I most often want to do is either (a) suppress all the
> footnotes or (b) get just the footnotes of type X and nothing else
> (not even the columns).
+1 for a way to do that, too. But it seems pretty much orthogonal to
what the display format details are.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | decibel | 2009-05-19 15:31:17 | Re: Show method of index |
| Previous Message | Sebastien FLAESCH | 2009-05-19 15:25:32 | Re: INTERVAL data type and libpq - what format? |