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

Re: 4s query want to run faster

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Adonias Malosso" <malosso(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: 4s query want to run faster
Date: 2008-02-21 21:25:35
Message-ID: dcc563d10802211325t365388f1te340e7f9b7e18dd3@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
Well, all the row counts in expected and actual are pretty close.  I'm
guessing it's as optimized as it's likely to get.  you could try
mucking about with random_page_cost to force index usage, but indexes
are not always a win in pgsql, hence the seq scans etc...  If the
number of rows returned represents a large percentage of the total
number of rows in the table, then a seq scan is generally a win.  Note
that most all the time being spent in this query is on the Hash Join,
not on the seq scans.

Also, you should really update to 8.2.6 the latest 8.2 version.  Check
the release notes for the bugs that were fixed between 8.2.1 and 8.2.6

In response to

pgsql-performance by date

Next:From: Mark KirkwoodDate: 2008-02-21 22:59:06
Subject: Re: 4s query want to run faster
Previous:From: Adonias MalossoDate: 2008-02-21 21:23:36
Subject: Re: 4s query want to run faster

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