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

Re: PG 8.3.3 - ERROR: lock AccessShareLock on object16385/16467/0 is already held

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Milligan <milli(at)acmeps(dot)com>, pgsql-bugs(at)postgreSQL(dot)org
Subject: Re: PG 8.3.3 - ERROR: lock AccessShareLock on object16385/16467/0 is already held
Date: 2008-12-29 15:16:24
Message-ID: 20081229151624.GH4545@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:

> 2008-09-15 21:56  tgl
> 
> 	* src/include/storage/: lock.h (REL8_1_STABLE), lock.h
> 	(REL8_3_STABLE), lock.h (REL8_0_STABLE), lock.h (REL8_2_STABLE),
> 	lock.h: Widen the nLocks counts in local lock tables from int to
> 	int64.

Doh, I didn't see it because I only checked the change log for lock.c,
not lock.h :-(

> > A customer of ours started hitting this bug too, last week.
> 
> Tut tut, customer not on latest point release?

Wouldn't be a first for them (we try hard, they don't necessarily heed
advice).

Thanks!

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

pgsql-bugs by date

Next:From: Alex HunsakerDate: 2008-12-29 22:07:25
Subject: ALTER TABLE DISABLE RULE does not work inside of a transaction
Previous:From: Tom LaneDate: 2008-12-29 15:06:18
Subject: Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held

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