Re: Optimizing a request
От | Josh Berkus |
---|---|
Тема | Re: Optimizing a request |
Дата | |
Msg-id | 200408311215.40812.josh@agliodbs.com обсуждение исходный текст |
Ответ на | Optimizing a request (Jean-Max Reymond <jmreymond@gmail.com>) |
Ответы |
Re: Optimizing a request
|
Список | 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
В списке pgsql-performance по дате отправления: