| From: | Együd Csaba <csegyud(at)vnet(dot)hu> |
|---|---|
| To: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "'Pgsql-General(at)Postgresql(dot)Org (E-mail)'" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Performance problem on RH7.1 |
| Date: | 2004-06-30 06:00:00 |
| Message-ID: | 002e01c45e67$7b546f30$230a0a0a@compaq |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
> Generally you want '=' conditions on the leftmost index keys; any
> inequality or range constraint should be on the rightmost
> keys. You can see this by thinking about the range of index entries that
> the scan will have to pass over.
I see. Just like in your earlier example, where you reduced the number of
index entries to pass over by giving the stockid, productid and the changeid
first.
Thank you very much.
Good luck,
-- Csaba Együd
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 2004. 06. 27.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Soeren Gerlach | 2004-06-30 06:26:57 | Slow dump with pg_dump/pg_restore ? How to improve ? |
| Previous Message | Joe Conway | 2004-06-30 05:26:07 | Re: minimum operators for b-tree, r-tree |