Re: "stuck spinlock"

On 2013-12-16 08:36:51 -0600, Merlin Moncure wrote:
> On Sat, Dec 14, 2013 at 6:20 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> > On 2013-12-13 15:49:45 -0600, Merlin Moncure wrote:
> >> Is this an edge case or something that will hit a lot of users?
> >> Arbitrary server panics seems pretty serious...
> >
> > Is your question about the bgworker part you're quoting or about the
> > stuck spinlock stuff? I don't think the bgworker bug is too bad in
> > practice but the one in handle_sig_alarm() stuff certainly is.
> >
> > I think while it looks possible to hit problems without statement/lock
> > timeout, it's relatively unlikely that those are hit in practice.
>
> Well, both -- I was just wondering out loud what the severity level of
> this issue was. In particular, is it advisable for the general public
> avoid this release? My read on this is 'probably'.

Hard to say, the issues fixed in the release are quite important as
well. I'd tend to say they are more important. I think we just need to
release 9.3.3 pretty soon.

The multixact fixes in 9.3.2 weren't complete either... (see recent push)

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services