Metacat

Matt suggested that xml_nodes table can probably be divided into multiple
tables based on the doctype. For example, xml_nodes can be divided into the
following:
1. xml_nodes_eml_2_0_0
2. xml_nodes_eml_2_0_1
3. xml_nodes_default

Hence any query for searching for a given text will be divided into 3 sub
queries, results of which can be unioned. While we are still going through the
same number of records (assuming the query is for all doctypes), this might
result in performance enhancement in a db like Oracle on a multi-proc machine.
From experience, Postgres will still run it on one proc... unless we run a
seperate query on each of the tables and union the results in the servlet

Though it is not clear how much performance would be achieved by this...