Re: pg_dump --pretty-print-views
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: David Fetter <david@fetter.org>, Marko Tiikkaja <pgmail@joh.to>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2013-01-10T17:35:00Z
Lists: pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes: > I think there's a very good case for breaking the nexus between > PRETTYFLAG_PAREN and PRETTYFLAG_INDENT+line wrapping for views. Only > PRETTYFLAG_PAREN affects the safety issue. The others are just about > white space in safe places. What I was actually thinking about was turning on indent/linewrapping all the time (ie, no change on pg_dump's side, just hack ruleutils). If we believe it's safe, why not just do it? It's the paren-removal that pg_dump can't tolerate. regards, tom lane