Skip site navigation (1) Skip section navigation (2)

Re: pg_dump --pretty-print-views

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Fetter <david(at)fetter(dot)org>, Marko Tiikkaja <pgmail(at)joh(dot)to>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump --pretty-print-views
Date: 2013-01-10 17:37:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 01/10/2013 12:35 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)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.

Works for me.



In response to


pgsql-hackers by date

Next:From: Josh BerkusDate: 2013-01-10 17:54:30
Subject: Save The Date: Cluster-Hackers meeting May 21st
Previous:From: Tom LaneDate: 2013-01-10 17:35:00
Subject: Re: pg_dump --pretty-print-views

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group