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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Milligan <milli(at)acmeps(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held
Date: 2008-08-30 00:28:06
Message-ID: 28948.1220056086@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Michael Milligan <milli(at)acmeps(dot)com> writes:
> Tom Lane wrote:
>> Once you've determined which table the error message is talking about,
>> please show us what the transaction does with that table.

> You mean like:

> BEGIN;
> PREPARE msg (...) INSERT INTO email VALUES (...);
> EXECUTE msg (...)
> EXECUTE msg (...)
> EXECUTE msg (...)
> EXECUTE msg (...)
> ... repeated millions of times
> COMMIT;

What I'm wondering about is the sequence of operations that are executed
per row.  Could it be long enough that the email table is being touched
by more than 2 billion separate SQL operations within the transaction?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Michael MilliganDate: 2008-08-30 00:48:05
Subject: Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held
Previous:From: Michael MilliganDate: 2008-08-29 22:44:22
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