From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Oleg Lebedev <oleg.lebedev@waterford.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: TPC-R benchmarks
Date: Wed, 08 Oct 2003 00:15:57 -0400
Message-ID: <29371.1065586557@sss.pgh.pa.us> (raw)
In-Reply-To: <200310071659.17863.josh@agliodbs.com>
References: <993DBE5B4D02194382EC8DF8554A52731D7661@postoffice.waterford.org>
<200310071659.17863.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> To sum up the below: it appears that whenever a set of WHERE conditions
> exceeds a certain level of complexity, the planner just ignores all
> applicable indexes and goes for a seq scan.
It looks to me like the planner is coercing the WHERE clause into
canonical OR-of-ANDs form (DNF). Which is often a good heuristic
but it seems unhelpful for this query.
> How can we fix this?
Feel free to propose improvements to the heuristics in
src/backend/optimizer/prep/prepqual.c ...
regards, tom lane
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: tgl@sss.pgh.pa.us, josh@agliodbs.com, oleg.lebedev@waterford.org
Subject: Re: TPC-R benchmarks
In-Reply-To: <29371.1065586557@sss.pgh.pa.us>
* 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