| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-core <pgsql-core(at)postgresql(dot)org> |
| Subject: | Re: [CORE] postpone next week's release |
| Date: | 2015-05-30 21:23:36 |
| Message-ID: | 1430A805-A080-4004-8112-4EA75713E773@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On May 30, 2015 2:19:00 PM PDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Andres Freund <andres(at)anarazel(dot)de> writes:
>> * The signal handling, sinval, client communication changes. Little
>to
>> none problems so far, but it's complex stuff. These changes are an
>> example of potential for problems due to changes to reduce
>> complexity...
>
>As far as that goes, it's quite clear from the buildfarm that the
>atomics stuff is not very stable on non-mainstream architectures.
Is that the case? So far it seems to primarily be a problem of the, old, barrier emulation being buggy (non reentrant). And that being visible due to the new barrier in the latch code.
If not be surprised if there were more bugs, don't get me wrong, this is highly platform dependant stuff.
---
Please excuse brevity and formatting - I am writing this on my mobile phone.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2015-05-30 21:46:58 | Re: nested loop semijoin estimates |
| Previous Message | Tom Lane | 2015-05-30 21:19:00 | Re: [CORE] postpone next week's release |