| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Neha Khatri <nehakhatri5(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Does pg_upgrade really support "make installcheck"? |
| Date: | 2017-06-08 15:02:16 |
| Message-ID: | 13769.1496934136@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> The whole thing is explained here:
> <https://www.postgresql.org/message-id/20327.1322435869@sss.pgh.pa.us>
> And since then the buildfarm has acquired a separate optional module
> that tests pg_upgrade. It's enabled by default in the sample config file.
> So it's not like we don't have buildfarm coverage - we do in fact.
> Re-enabling this in the Makefile would a) result in breakage on some
> members and b) make most members do redundant work.
> I vote for improving the docs.
WFM, I'll go do that (and maybe improve the comment in the makefile)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-06-08 15:18:28 | Re: List of hostaddrs not supported |
| Previous Message | Tom Lane | 2017-06-08 14:50:26 | Re: List of hostaddrs not supported |