| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: anole - test case sha2 fails on all branches |
| Date: | 2015-04-23 14:54:45 |
| Message-ID: | 489.1429800885@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Given that anole is the only one reporting this, I'm not sure that we
> should immediately blame Postgres itself. I have a vague recollection
> that we've seen this symptom before and traced it to a bug in some
> supporting library. Is anole using any particularly out-of-date versions
> of openssl, kerberos, etc?
A bit of digging in the archives suggests that my hindbrain remembered this:
http://www.postgresql.org/message-id/flat/4F5A8404(dot)8020708(at)dunslane(dot)net
The specifics probably don't apply to anole, but the conclusion that
inconsistent openssl header and library files triggered the bug might.
Maybe it'd be worth trying to see if we could detect such inconsistencies
during configure?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2015-04-23 15:00:43 | Re: tablespaces inside $PGDATA considered harmful |
| Previous Message | Geoff Winkless | 2015-04-23 14:52:40 | Re: INSERT ... ON CONFLICT IGNORE (and UPDATE) 3.0 |