| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Christophe Pettus <xof(at)thebuild(dot)com> |
| Subject: | Re: "stuck spinlock" |
| Date: | 2013-12-13 21:49:45 |
| Message-ID: | CAHyXU0z4+ehtoMhyMfy2uKMpVaJLZ+zS9kjf=-qZdb-sxkUA=g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 13, 2013 at 12:32 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Dec 13, 2013 at 11:26 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> And while we're on the subject ... isn't bgworker_die() utterly and
>> completely broken? That unconditional elog(FATAL) means that no process
>> using that handler can do anything remotely interesting, like say touch
>> shared memory.
>
> Yeah, but for the record (since I see I got cc'd here), that's not my
> fault. I moved it into bgworker.c, but it's been like that since
> Alvaro's original commit of the bgworker facility
> (da07a1e856511dca59cbb1357616e26baa64428e).
Is this an edge case or something that will hit a lot of users?
Arbitrary server panics seems pretty serious...
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2013-12-13 22:57:09 | Re: "stuck spinlock" |
| Previous Message | Alvaro Herrera | 2013-12-13 20:08:46 | Re: pgsql: Fix a couple of bugs in MultiXactId freezing |