pgsql: Repair PANIC condition in hash indexes when a previous index - Mailing list pgsql-committers

Log Message:
-----------
Repair PANIC condition in hash indexes when a previous index extension attempt
failed (due to lock conflicts or out-of-space).  We might have already
extended the index's filesystem EOF before failing, causing the EOF to be
beyond what the metapage says is the last used page.  Hence the invariant
maintained by the code needs to be "EOF is at or beyond last used page",
not "EOF is exactly the last used page".  Problem was created by my patch
of 2006-11-19 that attempted to repair bug #2737.  Since that was
back-patched to 7.4, this needs to be as well.  Per report and test case
from Vlastimil Krejcir.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
    pgsql/src/backend/access/hash:
        README (r1.4 -> r1.4.4.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/README.diff?r1=1.4&r2=1.4.4.1)
        hashovfl.c (r1.45.4.1 -> r1.45.4.2)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashovfl.c.diff?r1=1.45.4.1&r2=1.45.4.2)
        hashpage.c (r1.47.4.1 -> r1.47.4.2)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashpage.c.diff?r1=1.47.4.1&r2=1.47.4.2)
    pgsql/src/include/access:
        hash.h (r1.59 -> r1.59.4.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/hash.h.diff?r1=1.59&r2=1.59.4.1)