Re: userlock changes for 8.1/8.2
От | Jim C. Nasby |
---|---|
Тема | Re: userlock changes for 8.1/8.2 |
Дата | |
Msg-id | 20050125044040.GX67721@decibel.org обсуждение исходный текст |
Ответ на | Re: userlock changes for 8.1/8.2 (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Mon, Jan 24, 2005 at 10:43:40PM -0500, Tom Lane wrote: > "Jim C. Nasby" <decibel@decibel.org> writes: > > Speaking of other tricks and things missing; I'd like to see support for > > named locks. > > [ yawn... ] Create a table with a "name" column, put some rows in it, > lock the rows. What would guarantee that the OIDs of those rows don't conflict with some other OIDs in the system? BTW, this becomes a real issue if you're trying to write code that is meant to be incorporated into other PostgreSQL applications, which might also be using user_lock. Having a text-based means to identify locks greatly reduces the odds of conflicting with a userlock being used by an existing application. -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"
В списке pgsql-hackers по дате отправления: