| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| 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-29 20:13:21 |
| Message-ID: | 48B85861.9090200@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Michael Milligan | 2008-08-29 20:05:51 | PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held |