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

From Michael Milligan
Subject Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held
Date
Msg-id 48B86177.6030207@acmeps.com
Whole thread Raw
In response to Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-bugs
Heikki Linnakangas wrote:
> Michael Milligan wrote:
>> Uh oh.  This is a first (for me).  I got this error on a transaction, it
>> did not crash the server but did abort the transaction (of course).
>>
>> ERROR:  lock AccessShareLock on object 16385/16467/0 is already held
>>
>> What was I doing?  A large transaction where I was pushing about 20
>> million rows into two tables using prepared transactions.  I have been
>> doing this for some time (over a year) on 8.2.6 without any problems.
>
> Could you provide more details on the transaction? At what point did it
> fail, during the insertss, or at commit perhaps? Are you really using
> prepared transactions, aka two-phase commit, or did you mean prepared
> statements?

Yes, mistyped there, prepared _statements_.  It failed during an
EXECUTE, so during a prepared INSERT statement.

Regards,
Mike

--
Michael Milligan                                   -> milli@acmeps.com

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held
Next
From: Michael Milligan
Date:
Subject: Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held