| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | "<Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Dan Ports" <drkp(at)csail(dot)mit(dot)edu>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |
| Date: | 2011-06-03 20:44:03 |
| Message-ID: | 4DE90143020000250003E13C@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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.
Hmm. As mentioned earlier in the thread, cleaning these up doesn't
actually have any benefit beyond freeing space in the predicate
locking collections. I'm not sure that benefit is enough to justify
this much new mechanism. Maybe I should just leave them alone and
let them get cleaned up in due course with the rest of the locks.
Any opinions on that?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2011-06-03 20:48:22 | Re: Error in PQsetvalue |
| Previous Message | Bruce Momjian | 2011-06-03 20:42:05 | Re: Getting a bug tracker for the Postgres project |