Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held
| От | Tom Lane |
|---|---|
| Тема | Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held |
| Дата | |
| Msg-id | 28948.1220056086@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: 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
Re: PG 8.3.3 - ERROR: lock AccessShareLock on object 16385/16467/0 is already held |
| Список | pgsql-bugs |
Michael Milligan <milli@acmeps.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
В списке pgsql-bugs по дате отправления: