pgsql: Fix oversight in coding of _bt_start_vacuum: we can't assume that

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix oversight in coding of _bt_start_vacuum: we can't assume that
Date: 2007-03-30 00:12:59
Message-ID: 20070330001259.96BA99FBBCC@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix oversight in coding of _bt_start_vacuum: we can't assume that the LWLock
will be released by transaction abort before _bt_end_vacuum gets called.
If either of these "can't happen" errors actually happened, we'd freeze up
trying to acquire an already-held lock. Latest word is that this does
not explain Martin Pitt's trouble report, but it still looks like a bug.

Modified Files:
--------------
pgsql/src/backend/access/nbtree:
nbtutils.c (r1.82 -> r1.83)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtutils.c.diff?r1=1.82&r2=1.83)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-03-30 00:13:05 pgsql: Fix oversight in coding of _bt_start_vacuum: we can't assume that
Previous Message Bruce Momjian 2007-03-29 22:46:43 pgsql: pg_char_to_encoding() was redundant in initdb because