Re: LWLock deadlock and gdb advice

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Geoghegan <pg(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: LWLock deadlock and gdb advice
Date: 2015-07-30 16:03:01
Message-ID: CAMkU=1yKihyZK_Vbc7gnS5Q+Xh0h8BhtCWGybbbpiHeiZWAq9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 29, 2015 at 6:10 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:

> On 2015-07-29 14:22:23 +0200, Andres Freund wrote:
> > On 2015-07-29 15:14:23 +0300, Heikki Linnakangas wrote:
> > > Ah, ok, that should work, as long as you also re-check the variable's
> value
> > > after queueing. Want to write the patch, or should I?
> >
> > I'll try. Shouldn't be too hard.
>
> What do you think about something roughly like the attached?
>

I've not evaluated the code, but applying it does solve the problem I was
seeing.

Cheers,

Jeff

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2015-07-30 16:03:56 Re: pgbench stats per script & other stuff
Previous Message Tom Lane 2015-07-30 15:54:42 Re: Proposal: backend "niceness" / session_priority