Re: Using LIMIT changes index used by planner

From: Pierre-Frédéric Caillaud
Subject: Re: Using LIMIT changes index used by planner
Date: ,
Msg-id: opsjhpf9t8cq72hf@musicbox
(view: Whole thread, Raw)
In response to: Re: Using LIMIT changes index used by planner  (Tom Lane)
List: pgsql-performance

Tree view

Using LIMIT changes index used by planner  (Sven Willenberger, )
 Re: Using LIMIT changes index used by planner  (Andrew McMillan, )
  Re: Using LIMIT changes index used by planner  (Sven Willenberger, )
   Re: Using LIMIT changes index used by planner  (Tom Lane, )
    Re: Using LIMIT changes index used by planner  (Sven Willenberger, )
     Re: Using LIMIT changes index used by planner  (Tom Lane, )
    Re: Using LIMIT changes index used by planner  (Pierre-Frédéric Caillaud<>, )

On Mon, 13 Dec 2004 17:43:07 -0500, Tom Lane <> wrote:

> Sven Willenberger <> 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 ?


pgsql-performance by date:

From: Pierre-Frédéric Caillaud
Date:
Subject: Re: Caching of Queries
From: "Amrit Angsusingh"
Date:
Subject: Howto Increased performace ?