Skip site navigation (1) Skip section navigation (2)

Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held

From: daveg <daveg(at)sonic(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held
Date: 2011-09-08 00:55:59
Message-ID: 20110908005559.GQ24583@sonic.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Sep 07, 2011 at 07:39:15PM -0400, Tom Lane wrote:
> daveg <daveg(at)sonic(dot)net> writes:
> > Also, this is very intermittant, we have seen it only in recent months
> > on both 8.4.7 and 9.0.4 after years of no problems. Lately we see it what
> > feels like a few times a month. Possibly some new application behaviour
> > is provoking it, but I have no guesses as to what.
> 
> BTW ... what were the last versions you were running on which you had
> *not* seen the problem?  (Just wondering about the possibility that we
> back-patched some "fix" that broke things.  It would be good to have
> a version range before trawling the commit logs.)

The first version we saw it on was 8.4.7.

-dg
 
-- 
David Gould       daveg(at)sonic(dot)net      510 536 1443    510 282 0869
If simplicity worked, the world would be overrun with insects.

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-09-08 01:02:04
Subject: Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held
Previous:From: Brendan JurdDate: 2011-09-08 00:35:11
Subject: Re: Moving core timestamp typedefs/macros somewhere else

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group