From: Wei Weng <wweng@kencast.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alex Stapleton <alexs@advfn.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL using the wrong Index
Date: Mon, 13 Jun 2005 11:47:30 -0400
Message-ID: <42ADAA92.7000200@kencast.com> (raw)
In-Reply-To: <19854.1118674492@sss.pgh.pa.us>
References: <2D1A68BF-B3A4-490E-8053-3CF6626B8DAF@advfn.com>
<19854.1118674492@sss.pgh.pa.us>
Tom Lane wrote:
>
>
> This was just covered in excruciating detail yesterday ...
>
> You need to write
> order by symbol desc, time desc limit 1
> to get the planner to recognize the connection to the sort order
> of this index. Since you're only selecting one value of symbol,
> the actual output doesn't change.
>
Is this the right behavior (not a bug)? Is postgresql planning on changing
this soon?
Thanks
Wei
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: wweng@kencast.com, tgl@sss.pgh.pa.us, alexs@advfn.com
Subject: Re: PostgreSQL using the wrong Index
In-Reply-To: <42ADAA92.7000200@kencast.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