diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 1999-11-21 20:01:10 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 1999-11-21 20:01:10 +0000 |
| commit | 40d3e9254101d23c4f70b95d621277d306c7baf1 (patch) | |
| tree | d764a3f9b2da234c77677fb9254f7edab78d83fc /src/backend/utils/adt/arrayfuncs.c | |
| parent | 3047b444e81946bdc9e6f1b12f9c375e36aff1c9 (diff) | |
| download | postgresql-40d3e9254101d23c4f70b95d621277d306c7baf1.tar.gz postgresql-40d3e9254101d23c4f70b95d621277d306c7baf1.zip | |
index_destroy() must grab exclusive access to the parent table
of the index it wants to destroy. This ensures that no other backend is
actively scanning or updating that index. Getting exclusive access on
the index alone is NOT sufficient, because the executor is rather
cavalier about getting locks on indexes --- see ExecOpenIndices().
It might be better to grab index locks in the executor, but I'm not
sure the extra lockmanager traffic is really worth it just to make
index_destroy cleaner.
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions