| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fast default stuff versus pg_upgrade |
| Date: | 2018-06-21 12:07:58 |
| Message-ID: | 81d74f25-4960-f32a-92dc-8052e45704c9@2ndQuadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/20/2018 09:04 PM, Andres Freund wrote:
> Probably couldn't hurt to run the changed files through
> pgindent and fix the damage...
>
>
> Looks reasonable to me, but I've not tested it.
Thanks
Patch after pgindent attached. This will involve a catversion bump since
we're adding a new function.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| fix-default-6.patch | text/x-patch | 11.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2018-06-21 12:10:23 | Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query |
| Previous Message | Pavan Deolasee | 2018-06-21 11:25:50 | Re: PATCH: backtraces for error messages |