Alvaro Herrera b78647a0e6 Restrict infomask bits to set on multixacts ...

We must only set the bit(s) for the strongest lock held in the tuple;
otherwise, a multixact containing members with exclusive lock and
key-share lock will behave as though only a share lock is held.

This bug was introduced in commit 0ac5ad5134, somewhere along
development, when we allowed a singleton FOR SHARE lock to be
implemented without a MultiXact by using a multi-bit pattern.
I overlooked that GetMultiXactIdHintBits() needed to be tweaked as well.
Previously, we could have the bits for FOR KEY SHARE and FOR UPDATE
simultaneously set and it wouldn't cause a problem.

Per report from digoal@126.com

2013-01-31 19:35:31 -03:00

..

common

Improve concurrency of foreign key locking

2013-01-23 12:04:59 -03:00

gin

Update copyrights for 2013

2013-01-01 17:15:01 -05:00

gist

Add some randomness to the choice of which GiST page to insert to.

2013-01-25 16:58:38 +02:00

hash

Provide database object names as separate fields in error messages.

2013-01-29 17:08:26 -05:00

heap

Restrict infomask bits to set on multixacts

2013-01-31 19:35:31 -03:00

index

Update copyrights for 2013

2013-01-01 17:15:01 -05:00

nbtree

Provide database object names as separate fields in error messages.

2013-01-29 17:08:26 -05:00

rmgrdesc

Fast promote mode skips checkpoint at end of recovery.

2013-01-29 00:06:15 +00:00

spgist

Update copyrights for 2013

2013-01-01 17:15:01 -05:00

transam

Switch timelines if we crash soon after promotion.

2013-01-31 19:29:32 +00:00

Makefile

Split out rmgr rm_desc functions into their own files

2012-11-28 13:01:15 -03:00