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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-performance by date

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