pgsql: Found the problem with my operator-family changes: by fetching

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Found the problem with my operator-family changes: by fetching
Date: 2006-12-31 20:32:04
Message-ID: 20061231203204.F23D09FA097@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Found the problem with my operator-family changes: by fetching from
pg_opclass during LookupOpclassInfo(), I'd turned pg_opclass_oid_index
into a critical system index. However the problem could only manifest
during a backend's first attempt to load opclass data, and then only
if it had successfully loaded pg_internal.init and subsequently received
a relcache flush; which made it impossible to reproduce in sequential
tests and darn hard even in parallel tests. Memo to self: when
exercising cache flush scenarios, must disable LookupOpclassInfo's
internal cache too.

Modified Files:
--------------
pgsql/src/backend/utils/cache:
relcache.c (r1.251 -> r1.252)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/cache/relcache.c.diff?r1=1.251&r2=1.252)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2007-01-02 10:38:45 Re: Loose ends in PG XML patch
Previous Message User Cmaj 2006-12-31 02:23:25 pgaccess - pgaccess: clear out initial radio button state automatically