From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | decibel <decibel(at)decibel(dot)org> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, 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:44:25 |
Message-ID: | 14933.1242747865@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
decibel <decibel(at)decibel(dot)org> writes:
> On May 19, 2009, at 10:27 AM, Tom Lane wrote:
>> +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 ...
> Hmm.... what if we made the default to be all-tabular output, but had
> a different command that would spit out the SQL to re-create something?
Well, we already have something that's intended to recreate stuff;
it's called pg_dump. The issue from my point of view is trying to
reproduce problems based on what people post to the lists --- which
very often is \d output. It will not help me if there is some
nondefault variant of \d that emits clean SQL, because that won't be
what gets posted.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-05-19 15:52:25 | Re: Show method of index |
Previous Message | decibel | 2009-05-19 15:31:17 | Re: Show method of index |