diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2008-04-16 18:23:19 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2008-04-16 18:23:19 +0000 |
| commit | 5132e34005b6db2fab7d1b777592d0fe38520f46 (patch) | |
| tree | f6593bfa7e5ed9dc0c4da398633022a731fc64e3 /src/backend/access/gist/gist.c | |
| parent | 79522dfb35301eb13b2b94a9b09501a2169cdfc6 (diff) | |
| download | postgresql-5132e34005b6db2fab7d1b777592d0fe38520f46.tar.gz postgresql-5132e34005b6db2fab7d1b777592d0fe38520f46.zip | |
Fix LOAD_CRIT_INDEX() macro to take out AccessShareLock on the system index
it is trying to build a relcache entry for. This is an oversight in my 8.2
patch that tried to ensure we always took a lock on a relation before trying
to build its relcache entry. The implication is that if someone committed a
reindex of a critical system index at about the same time that some other
backend were starting up without a valid pg_internal.init file, the second one
might PANIC due to not seeing any valid version of the index's pg_class row.
Improbable case, but definitely not impossible.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions