On Apr 5, 2011, at 7:35 AM, rihad wrote:
> No, what I meant was that we're already using ints for a different purpose in another app on the same server, so I
cannotsafely reuse them. Aren't advisory lock ID's unique across the whole server? The sole purpose of the string ID is
tobe able to supply an initial namespace prefix ("foo.NNN") so NNN wouldn't clash in different subsystems of the app.
MySQLis pretty convenient in this regard. Now I think it would be easier for me to work around this Postgres limitation
bysimply LOCKing on some table (maybe one created specifically as something to lock on to) instead of using
pg_advisory_lockexplicitly.
Simply locking tables might be easy, but probably won't be optimal. Why are you using advisory locks at all? They
certainlyhave their place, but they can also be an overused crutch, especially for people less familiar with MVCC.
