Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
pgsql: Fix failure to check for INVALID worker entry in the new
- From: alvherre(at)postgresql(dot)org (Alvaro Herrera)
- To: pgsql-committers(at)postgresql(dot)org
- Subject: pgsql: Fix failure to check for INVALID worker entry in the new
- Date: Wed, 2 May 2007 12:47:14 -0300 (ADT)
- Message-id: <20070502154714.37CC39FBCB3@postgresql.org> <text/plain>
Log Message:
-----------
Fix failure to check for INVALID worker entry in the new autovacuum code, which
could happen when a worker took to long to start and was thus "aborted" by the
launcher. Noticed by lionfish buildfarm member.
Modified Files:
--------------
pgsql/src/backend/postmaster:
autovacuum.c (r1.42 -> r1.43)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/autovacuum.c.diff?r1=1.42&r2=1.43)
- Prev by Date: pgsql: Fix oversight in PG_RE_THROW processing: it's entirely possible
- Next by Date: pgsql: Use the new TimestampDifferenceExceeds API instead of
- Previous by thread: pgsql: Fix oversight in PG_RE_THROW processing: it's entirely possible
- Next by thread: pgsql: Use the new TimestampDifferenceExceeds API instead of
- Indexes: