| From: | Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, glyn(at)8kb(dot)co(dot)uk |
| Subject: | Re: Opossum vs. float4 NaN |
| Date: | 2019-01-27 10:29:20 |
| Message-ID: | 1970445535.2776083.1548584960750@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> On Saturday, 26 January 2019, 16:00:24 GMT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: >>
>> I'm thinking we should regretfully retire opossum, unless there's
>> a software update available for it that fixes this bug.
I'm happy to update opossum to see if the issue goes away; likewise I'm just as happy to retire it completely. It'll still come online occasionally regardless, so makes no difference.
I guess the main question is; does anybody care about builds on a 20 year old netbsd/mipsel dinosaur? I noticed there are now mips64el and mips64eb build-farm members.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2019-01-27 10:50:15 | Re: jsonpath |
| Previous Message | Simon Riggs | 2019-01-27 08:00:31 | Re: Allowing extensions to supply operator-/function-specific info |