| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fast default stuff versus pg_upgrade |
| Date: | 2018-06-21 17:31:48 |
| Message-ID: | c1ec4f5c-8753-7363-b01f-43431f486394@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-06-21 17:40:08 | Re: Fast default stuff versus pg_upgrade |
| Previous Message | Heikki Linnakangas | 2018-06-21 17:30:03 | Re: location reporting in TAP test failures |