Re: Simply join in PostrgeSQL takes too long

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Vitaly Belman <vitalib(at)012(dot)net(dot)il>, Manfred Koizar <mkoi-pg(at)aon(dot)at>
Cc: Rod Taylor <pg(at)rbt(dot)ca>, Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Simply join in PostrgeSQL takes too long
Date: 2004-04-29 22:10:08
Message-ID: 200404291510.08757.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Vitaly,

> I am in the middle of going through them all, till now disabling the
> enable_mergejoin really helped.

In that case, your random_page_cost is probably too low. Check the ratio of
per-tuple times on index vs. seqscan seeks.

--
-Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Gary Doades 2004-04-29 22:31:00 Re: planner/optimizer question
Previous Message Tom Lane 2004-04-29 21:54:31 Re: planner/optimizer question