Re: Performance problem on RH7.1 - Mailing list pgsql-general

From Együd Csaba
Subject Re: Performance problem on RH7.1
Date
Msg-id 002e01c45e67$7b546f30$230a0a0a@compaq
Whole thread Raw
In response to Re: Performance problem on RH7.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.



pgsql-general by date:

Previous
From: Joe Conway
Date:
Subject: Re: minimum operators for b-tree, r-tree
Next
From: Soeren Gerlach
Date:
Subject: Slow dump with pg_dump/pg_restore ? How to improve ?