From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Adding \ev view editor? |
Date: | 2009-09-21 19:03:24 |
Message-ID: | 23820.1253559804@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> It might be worth pointing out that what I don't want pg_dump doing
>> is suppressing "useless" parentheses. Adding whitespace ought to be
>> safe enough. So if anyone wanted to do the work of decoupling those
>> two effects of the prettyprint option, we could have "semi pretty
>> printed" output in pg_dump. Dunno if it's worth it.
> The attached patch goes part of the way towards doing this, by adding
> white space unconditionally to the target list of a viewdef.
That's not what I had in mind by "decoupling" the option's effects.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2009-09-21 19:09:32 | Progress on Writeable CTEs |
Previous Message | Andrew Dunstan | 2009-09-21 18:26:05 | Re: Adding \ev view editor? |