Michael Hostbaek wrote:
Hi,1. Probably your query can't use index on table partno_lookup.partno_alias.
I am running postgresql 7.2.3 on a test server (with potential of
becoming my production server).
On the server I have a perl script, that is grabbing some data from a
inventory database (local) - with some subselects.
The query is like this:
my $sth = $ppdb->prepare("
select partno, create_date, mfg, condition, gescode, qty,
cmup,(SELECT partno_main FROM partno_lookup where partno_lookup.partno_alias ilike (?|| inventory.partno ||?) and mfg
ilike ? limit 1) as partno_main, (SELECT subcat FROM partno_lookup where
partno_lookup.partno_alias ilike (?|| inventory.partno ||?) and mfg ilike ? limit 1) as subcat, (SELECT key_search FROM partno_lookup where
partno_lookup.partno_alias ilike (?|| inventory.partno ||?) and mfg ilike ? limit 1) as key_search,
(SELECT text_desc FROM descriptions where
descriptions.partno=(SELECT partno_main FROM partno_lookup where partno_lookup.partno_alias ilike (?|| inventory.partno ||?)
and mfg ilike ? limit 1) limit 1) as descri from inventory where mfg ilike ? and ? <
create_date $refurbed order by key_search,
subcat, partno_main, status DESC ");
Consider creating table aliases which contains all possible parts aliases. You can change then "ilike" into "=" which will use indexes.
2. You don't need subselects in your query. You can change them into ordinary
table joins and use "group by" or "distinct on". In your case selecting from
partno_lookup is executed several times per one row.
3. Explain analyze would be helpful like in most performance cases...
The same with SQL query instead of Perl script.
4. This is rather a sql problem, than hardware/configuration one.
Regards,
Tomasz Myrta
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
