From: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
To: pgsql-performance@postgresql.org
Subject: Re: Using LIMIT changes index used by planner
Date: Fri, 24 Dec 2004 03:05:59 +0100
Message-ID: <opsjhpf9t8cq72hf@musicbox> (raw)
In-Reply-To: <28820.1102977787@sss.pgh.pa.us>
References: <41BD3317.9090507@dmv.com>
<1102931789.11712.9.camel@lamb.mcmillan.net.nz>
<41BE1270.7060908@dmv.com>
<28820.1102977787@sss.pgh.pa.us>
On Mon, 13 Dec 2004 17:43:07 -0500, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Sven Willenberger <sven@dmv.com> writes:
>> explain analyze select storelocation,order_number from custacct where
>> referrer = 1365 and orderdate between '2004-12-07' and '2004-12-07
>> 12:00:00' order by custacctid limit 10;
why not create an index on referrer, orderdate ?
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: lists@boutiquenumerique.com
Subject: Re: Using LIMIT changes index used by planner
In-Reply-To: <opsjhpf9t8cq72hf@musicbox>
* 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