Re: SIREAD lock versus ACCESS EXCLUSIVE lock
| От | Tom Lane |
|---|---|
| Тема | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
| Дата | |
| Msg-id | 26005.1307204344@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: SIREAD lock versus ACCESS EXCLUSIVE lock (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
| Ответы |
Re: SIREAD lock versus ACCESS EXCLUSIVE lock
|
| Список | pgsql-hackers |
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> On 03.06.2011 21:04, Kevin Grittner wrote:
>> Also, if anyone has comments or hints about the placement of those
>> calls, I'd be happy to receive them.
> heap_drop_with_catalog() schedules the relation for deletion at the end
> of transaction, but it's still possible that the transaction aborts and
> the heap doesn't get dropped after all. If you put the
> DropAllPredicateLocksFromTable() call there, and the transaction later
> aborts, you've lost all the locks already.
But on the third thought: is that wrong? Surely locks taken by an
aborted transaction can be discarded.
regards, tom lane
В списке pgsql-hackers по дате отправления: