Log Message:
-----------
Repair very-low-probability race condition between relation extension
and VACUUM: in the interval between adding a new page to the relation
and formatting it, it was possible for VACUUM to come along and decide
it should format the page too. Though not harmful in itself, this would
cause data loss if a third transaction were able to insert tuples into
the vacuumed page before the original extender got control back.
Tags:
----
REL7_4_STABLE
Modified Files:
--------------
pgsql/src/backend/access/heap:
hio.c (r1.50 -> r1.50.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/heap/hio.c.diff?r1=1.50&r2=1.50.2.1)
pgsql/src/backend/access/nbtree:
nbtpage.c (r1.72 -> r1.72.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtpage.c.diff?r1=1.72&r2=1.72.2.1)
nbtree.c (r1.106 -> r1.106.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtree.c.diff?r1=1.106&r2=1.106.2.1)
pgsql/src/backend/commands:
vacuumlazy.c (r1.32 -> r1.32.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.32&r2=1.32.2.1)
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
