Skip site navigation (1) Skip section navigation (2)

Re: Performance problem on RH7.1

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 (view raw, whole thread or download thread mbox)
Lists: pgsql-general

> 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

Thank you very much.

Good luck,
  -- Csaba Együd

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
Version: 6.0.712 / Virus Database: 468 - Release Date: 2004. 06. 27.

In response to

pgsql-general by date

Next:From: Soeren GerlachDate: 2004-06-30 06:26:57
Subject: Slow dump with pg_dump/pg_restore ? How to improve ?
Previous:From: Joe ConwayDate: 2004-06-30 05:26:07
Subject: Re: minimum operators for b-tree, r-tree

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group