From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: new psql \d command |
Date: | 2003-08-07 15:53:11 |
Message-ID: | 3F3275E7.6070200@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>Tom Lane wrote:
>
>
>>Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>>
>>
>>>It might be a bit risky getting pg_dump to use it though?
>>>
>>>
>>I definitely don't want pg_dump using the pretty-print stuff ;-).
>>I'm neutral on whether to use it in psql's \d commands.
>>
>>
>
>I thought the pretty-printing stuff was designed specifically for psql
>\d and third-party apps like pgadmin.
>
Yes it was, but it can be meaningful for pg_dump too.
The pretty-print stuff will inflate the dump with many spaces which
doesn't make any sense with formats not meant to be read by humans,
(--format=c), but --format=p output might well be used for user editing.
So IMHO an option to enable pretty-dump can be useful.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-08-07 16:00:48 | Re: new psql \d command |
Previous Message | Bruce Momjian | 2003-08-07 15:28:35 | Re: new psql \d command |