On Wed, Apr 27, 2016 at 10:57 AM, Bruce Momjian <br...@momjian.us> wrote: > Agreed. Sounds like a good plan --- a better plan than I have used in > the past.
Thinking about this a bit more, what I am inclined to do is: 1. Run pgindent. 2. Read the diff and revert any changes that look icky. 3. Commit the rest. 4. Run pgindent again and post the diff. Discuss how to fix the ickiness contained therein, then proceed accordingly. How does that sound? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
