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

Re: Optimizing a request

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Jean-Max Reymond <jmreymond(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Optimizing a request
Date: 2004-08-31 19:15:40
Message-ID: 200408311215.40812.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-performance
Jean,

> I have the following structure in my base 7.4.2

Upgrade to 7.4.5.  The version you're using has several known issues with data 
restore in the event of system failure.

> Hash Join  (cost=8.27..265637.59 rows=25 width=130)
>   Hash Cond: ("outer".rub_id = "inner".rub_id)
>   ->  Seq Scan on article  (cost=0.00..215629.00 rows=10000000 width=108)
>   ->  Hash  (cost=8.26..8.26 rows=3 width=22)
>         ->  Index Scan using rubrique_parent on rubrique
> (cost=0.00..8.26 rows=3 width=22)
>               Index Cond: (rub_parent = 8)

Those look suspiciously like stock estimates.  When was the last time you ran 
ANALYZE?


-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

pgsql-performance by date

Next:From: Jean-Max ReymondDate: 2004-08-31 19:19:09
Subject: Re: Optimizing a request
Previous:From: William YuDate: 2004-08-31 19:15:22
Subject: Re: Table UPDATE is too slow

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