From: | Michael Milligan <milli(at)acmeps(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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-29 20:52:07 |
Message-ID: | 48B86177.6030207@acmeps.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)acmeps(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Milligan | 2008-08-29 20:57:55 | Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held |
Previous Message | Tom Lane | 2008-08-29 20:28:59 | Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held |