From: Josh Berkus <josh@agliodbs.com>
To: Achilleus Mantzios <achill@matrix.gatewaynet.com>
To: Hannu Krosing <hannu@tm.ee>
Cc: pgsql-performance@postgresql.org
Subject: Re: An unresolved performance problem.
Date: Wed, 7 May 2003 08:26:52 -0700
Message-ID: <200305070826.52382.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305071700530.28446-100000@matrix.gatewaynet.com>
References: <Pine.LNX.4.44.0305071700530.28446-100000@matrix.gatewaynet.com>
Achilleus,
> My systems are (rather usual) linux/freebsd and the costs defined (by
> default) in postgresql.conf worked well for all queries except
> a cursed query on a cursed table.
> So i start to believe its an estimation selectivity
> problem.
We can probably fix the problem by re-writing the query then; see my previous
example this weekend about overdetermining criteria in order to force the use
of an index.
How about posting the query and the EXPLAIN ANALYZE results?
--
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-sql@postgresql.org
Cc: josh@agliodbs.com, achill@matrix.gatewaynet.com, hannu@tm.ee, pgsql-performance@postgresql.org
Subject: Re: An unresolved performance problem.
In-Reply-To: <200305070826.52382.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