Horton

Re: Fast default stuff versus pg_upgrade

Andrew Dunstan <andrew.dunstan@2ndquadrant.com>

View thread View on postgr.es
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org
Date: 2018-06-21T17:31:48Z
Lists: pgsql-hackers 

On 06/21/2018 12:08 PM, Tom Lane wrote:
> I wrote:
>> We could do without the unrelated whitespace changes in dumpDefaultACL,
>> too (or did pgindent introduce those?  Seems surprising ... oh, looks
>> like "type" has somehow snuck into typedefs.list.  Time for another
>> blacklist entry.)
> Hmm .. actually, "type" already is in pgindent's blacklist.  Are you
> using an up-to-date pgindent'ing setup?
>
> 			



I am now, This was a holdover from before I updated.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Allow for pg_upgrade of attributes with missing values