diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2005-12-03 05:51:03 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2005-12-03 05:51:03 +0000 |
commit | a98871b7ac601b4ebe6ba050b1f9cbfdd5d71ded (patch) | |
tree | 14a0b7c6a91cf05fc5556a6dcb00246ff11b0e6a /src/backend/executor/nodeIndexscan.c | |
parent | 1cf65140d07527e01c56164caefb5eb0c8106480 (diff) | |
download | postgresql-a98871b7ac601b4ebe6ba050b1f9cbfdd5d71ded.tar.gz postgresql-a98871b7ac601b4ebe6ba050b1f9cbfdd5d71ded.zip |
Tweak indexscan machinery to avoid taking an AccessShareLock on an index
if we already have a stronger lock due to the index's table being the
update target table of the query. Same optimization I applied earlier
at the table level. There doesn't seem to be much interest in the more
radical idea of not locking indexes at all, so do what we can ...
Diffstat (limited to 'src/backend/executor/nodeIndexscan.c')
-rw-r--r-- | src/backend/executor/nodeIndexscan.c | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/src/backend/executor/nodeIndexscan.c b/src/backend/executor/nodeIndexscan.c index 4beecfbd57f..94495b4bc71 100644 --- a/src/backend/executor/nodeIndexscan.c +++ b/src/backend/executor/nodeIndexscan.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/executor/nodeIndexscan.c,v 1.108 2005/12/02 20:03:40 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/executor/nodeIndexscan.c,v 1.109 2005/12/03 05:51:02 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -461,6 +461,7 @@ ExecInitIndexScan(IndexScan *node, EState *estate) { IndexScanState *indexstate; Relation currentRelation; + bool relistarget; /* * create state structure @@ -557,14 +558,19 @@ ExecInitIndexScan(IndexScan *node, EState *estate) ExecAssignScanType(&indexstate->ss, RelationGetDescr(currentRelation), false); /* - * open the index relation and initialize relation and scan descriptors. + * Open the index relation and initialize relation and scan descriptors. * Note we acquire no locks here; the index machinery does its own locks * and unlocks. (We rely on having a lock on the parent table to - * ensure the index won't go away!) + * ensure the index won't go away!) Furthermore, if the parent table + * is one of the target relations of the query, then InitPlan already + * opened and write-locked the index, so we can tell the index machinery + * not to bother getting an extra lock. */ indexstate->iss_RelationDesc = index_open(node->indexid); + relistarget = ExecRelationIsTargetRelation(estate, node->scan.scanrelid); indexstate->iss_ScanDesc = index_beginscan(currentRelation, indexstate->iss_RelationDesc, + !relistarget, estate->es_snapshot, indexstate->iss_NumScanKeys, indexstate->iss_ScanKeys); |