Re: pretty print viewdefs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pretty print viewdefs
Date
Msg-id 20874.1251397042@sss.pgh.pa.us
Whole thread Raw
In response to Re: pretty print viewdefs  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pretty print viewdefs  (Andrew Dunstan <andrew@dunslane.net>)
Re: pretty print viewdefs  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> OK, and how are we going to set that flag? Like I did, with a separate 
> function?

I would be inclined to invent a variant of pg_get_viewdef with an
additional parameter rather than choosing a new function name, but
otherwise yeah.  Or we could decide this isn't worth all the
trouble and just go back to your original patch.  By the time you
get done with all the documentation and client-side hacking that
would be required, this patch is going to be a lot larger than it
seems worth.

> I assume you are in effect saying you don't mind if there is an 
> occasional blank line in the output.

What blank line?  I would expect prettyprinting of expressions to
sometimes insert an embedded newline, but not one at the beginning
or end.  Do you have a counterexample?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: hot standby - merged up to CVS HEAD
Next
From: Andrew Dunstan
Date:
Subject: Re: pretty print viewdefs