Pavan Deolasee wrote: > together. In the SELECT path, we conditionally try for exclusive lock. If > the exclusive lock is also cleanup lock, we prune and defrag the page. > As the patch stands, during index fetch we try to prune only the chain > originating at that tuple. I am wondering if we should change that > and prune all the tuple chains in the page ?
I am thinking we are best just doing the index chain we already have to read. If you are modifying the table (like with UPDATE) it makes sense to be more aggressive and do the whole page because you know there are probably other table modifications, but for an index lookup there isn't any knowledge of whether the table is being modified so looking at more than we need seems like overkill. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
