Simon Riggs <[email protected]> writes:
> On Thu, May 3, 2012 at 5:04 PM, Tom Lane <[email protected]> wrote:
>> 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.
> Is that even an issue? Do we really want an overlapping lock space?
> AFAICS you'd either use transactional or session level, but to use
> both seems bizarre.
I dunno. That's the existing user-visible semantics, and I wasn't
proposing that we revisit the behavior. It's a bit late for such
a proposal given this already shipped in 9.1.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
