On Thu, May 3, 2012 at 11:04 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > I'm inclined to think that a saner implementation would involve > splitting the userlock lockmethod into two, one transactional and one > not. That gets rid of the when-to-release kluges, but instead we have > to think of a way for two different lockmethods to share the same > lock keyspace. If we don't split it then we definitely need to figure > out someplace else to keep the transactionality flag.
hm, would that be exposed through the pg_locks view? some users might be running queries like "select * from pg_locks where locktype='advisory' and ..." it's a minor point, but ideally if they share the same lockspace the same locktype would be reported in the view. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
