Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

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: Sun, 31 Dec 2006 16:32:04 -0400 (AST)
  • Message-id: <20061231203204.F23D09FA097@postgresql.org> <text/plain>

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)



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group