Marko Tiikkaja <pgmail(at)joh(dot)to> writes:
> While we can do the actual splitting of objects from a -Fc dump 
> relatively easily, we can't fix the view definitions after they've been 
> dumped.  So I'm proposing a --pretty-print-views setting to pg_dump 
> (patch attached).

-1.  The reason that pg_dump does not pretty-print things is that
it's unsafe; there is no real guarantee that the view will reload as
intended, because it's under-parenthesized.  (Even if we were sure
it would reload safely into current code, which I'm not, what of
future versions that could have different operator precedences?)

I don't think we should offer a foot-gun option like this at all,
and as for making it the default, not bloody likely.

I think your schema-diffing needs would be better served by a tool
specifically directed at that problem; which pg_dump is not, but
I believe there are some out there.

			regards, tom lane

In response to

• pg_dump --pretty-print-views at 2013-01-10 12:23:10 from Marko Tiikkaja

Responses

• Re: pg_dump --pretty-print-views at 2013-01-10 16:51:44 from David Fetter

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2013-01-10 16:32:35
	Subject: Re: PL/perl should fail on configure, not make
Previous:	From: Dimitri Fontaine	Date: 2013-01-10 16:14:28
	Subject: Re: in-catalog Extension Scripts and Control parameters (templates?)