Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Thu, 29 Mar 2007 21:12:59 -0300 (ADT)
- Message-id: <20070330001259.96BA99FBBCC@postgresql.org> <text/plain>
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)
- Prev by Date: pgsql: pg_char_to_encoding() was redundant in initdb because
- Next by Date: pgsql: Fix oversight in coding of _bt_start_vacuum: we can't assume that
- Previous by thread: pgsql: pg_char_to_encoding() was redundant in initdb because
- Next by thread: pgsql: Fix oversight in coding of _bt_start_vacuum: we can't assume that
- Indexes: