Re: SIREAD lock versus ACCESS EXCLUSIVE lock
| От | Tom Lane |
|---|---|
| Тема | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
| Дата | |
| Msg-id | 7904.1307130375@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: SIREAD lock versus ACCESS EXCLUSIVE lock ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
| Ответы |
Re: SIREAD lock versus ACCESS EXCLUSIVE lock
|
| Список | pgsql-hackers |
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
>> I think you'll need to just memorize the lock deletion command in
>> a backend-local list, and perform the deletion in a post-commit
>> function. Something similar to the PendingRelDelete stuff in
>> storage.c. In fact, hooking into smgrDoPendingDeletes would work,
>> but that seems like a modularity violation.
> Thanks. That's helpful. Will look at that code and do something
> similar.
Keep in mind that it's too late to throw any sort of error post-commit.
Any code you add there will need to have negligible probability of
failure.
regards, tom lane
В списке pgsql-hackers по дате отправления: