Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held
| От | Heikki Linnakangas |
|---|---|
| Тема | Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held |
| Дата | |
| Msg-id | 48B85861.9090200@enterprisedb.com обсуждение исходный текст |
| Ответ на | PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held (Michael Milligan <milli@acmeps.com>) |
| Ответы |
Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0
is already held
|
| Список | 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
В списке pgsql-bugs по дате отправления: