Project

General

Profile

Actions

Bug #2153

closed

Metacat Performace: Add/drop indices on key columns

Added by Saurabh Garg almost 19 years ago. Updated over 16 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
metacat
Target version:
Start date:
07/13/2005
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2153

Description

From Matt's email...

DB indices aren't created on some key columns such as
xml_nodes.nodedata (originally because indices weren't supported on
fields that big). This means a full table scan of the 6.5M records in
xml_nodes for every query. We need to inspect for missing indices and
create them, and need to consider the effect of UPPER on these indices
in case-insensitive queries and be sure to create corresponding UPPER
indices too. Once the indices are in place we need to check EXPLAIN to
be sure the optimizer is using the indices instead of doing table scans
(see http://www.postgresql.org/docs/faqs.FAQ.html#4.7). Also, indices
slow down inserts and updates, so any that aren't in use should be
dropped, which will take some analysis of the running DB (but this is
low priority comparatively speaking).


Related issues

Blocked by Metacat - Bug #1879: Metacat Performance: SummaryNewJing Tao01/18/2005

Actions
Actions

Also available in: Atom PDF