Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Optimizing a huge_table/tiny_table join
- From: PFC <lists(at)peufeu(dot)com>
- To: kynn(at)panix(dot)com, pgsql-performance(at)postgresql(dot)org
- Subject: Re: Optimizing a huge_table/tiny_table join
- Date: Wed, 31 May 2006 00:37:03 +0200
SELECT * FROM huge_table h, tiny_table t WHERE UPPER( h.id ) = UPPER( t.id )
What about :SELECT * FROM huge_table h WHERE UPPER(id) IN (SELECT upper(id) FROM tiny_table t)
Or, try opening a cursor on your original query and using FETCH. It might result in a different plan.
Or lower random_page_cost.
- References:
- Optimizing a huge_table/tiny_table join
- From: kynn
- Optimizing a huge_table/tiny_table join
- Prev by Date: Re: INSERT OU UPDATE WITHOUT SELECT?
- Next by Date: Re: INSERT OU UPDATE WITHOUT SELECT?
- Previous by thread: Optimizing a huge_table/tiny_table join
- Next by thread: Optimizing a huge_table/tiny_table join
- Indexes: