| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Time to retire Windows XP buildfarm host? |
| Date: | 2016-12-05 16:17:47 |
| Message-ID: | 17385.1480954667@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Windows XP has been past end of life for quite some time. Nevertheless I
> have kept my instance running with three buildfarm members: frogmouth,
> currawong and brolga. Howeever, a recent commit (apparently fa2fa99, but
> I'm not 100% sure) started causing a compiler segmentation fault on
> frogmouth, the mingw/gcc-4.5.0 animal running on this machine.
> ...
> Does anyone have any strong opinion in favor of keeping any of these
> animals running?
Hm, a look through our commit logs finds multiple mentions of each of
these animals as having been the only one showing a particular portability
issue. So I'm worried about loss of portability coverage. Are you sure
that the animals' build options and choices of toolchains are replicated
elsewhere?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-12-05 16:28:31 | Re: Tackling JsonPath support |
| Previous Message | Pantelis Theodosiou | 2016-12-05 16:04:30 | Re: missing optimization - column <> column |