| From: | Gary Chambers <gwchamb(at)gwcmail(dot)com> |
|---|---|
| To: | Chris Angelico <rosuav(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Warning: you don't own a lock of type ExclusiveLock |
| Date: | 2012-02-09 18:55:30 |
| Message-ID: | alpine.DEB.2.00.1202091347180.25264@equinox.garychambers.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Chris,
> pg_advisory_unlock (along with the other functions in that family) works
> on a set of mythical objects with no actual meaning beyond what the
> database administrator chooses to give them.
Thank you for your excellent description. I have never used the advisory
lock functionality that Postgres provides, and your reply combined with
Merlin's multi-part primer on them, it's easy to see their value,
application, and implementation.
Finally, with respect to my original request, it's quite conceivable that
the application is attempting to free the lock more times than it requested
it. Thank you again for your reply!
-- Gary Chambers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2012-02-09 20:50:46 | Re: Strategy for Primary Key Generation When Populating Table |
| Previous Message | Scott Marlowe | 2012-02-09 17:18:44 | Re: Strategy for Primary Key Generation When Populating Table |