From: Josh Berkus <josh@agliodbs.com>
To: Vitaly Belman <vitalib@012.net.il>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Rod Taylor <pg@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Simply join in PostrgeSQL takes too long
Date: Thu, 29 Apr 2004 15:10:08 -0700
Message-ID: <200404291510.08757.josh@agliodbs.com> (raw)
In-Reply-To: <147254626500.20040430000936@012.net.il>
References: <282909734.20040428002740@012.net.il>
<tlpu80tqhmnpc2sl63boejki6o4vbn1p3q@email.aon.at>
<147254626500.20040430000936@012.net.il>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, vitalib@012.net.il, mkoi-pg@aon.at, pg@rbt.ca
Subject: Re: Simply join in PostrgeSQL takes too long
In-Reply-To: <200404291510.08757.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox