diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-12-31 20:32:04 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-12-31 20:32:04 +0000 |
commit | 0b56be83441c01419fcf82ebe666e968e6f7b246 (patch) | |
tree | 77aafcc3cb26fcdc5284844227cedf88c6f7957a /src/backend/utils/adt/float.c | |
parent | 5725b9d9afc8c3ba24e94cbc7020889fe8ad7ef9 (diff) | |
download | postgresql-0b56be83441c01419fcf82ebe666e968e6f7b246.tar.gz postgresql-0b56be83441c01419fcf82ebe666e968e6f7b246.zip |
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.
Diffstat (limited to 'src/backend/utils/adt/float.c')
0 files changed, 0 insertions, 0 deletions