From: Mr Pink <mr_pink_is_the_only_pro@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: Re: Why does a simple query not use an obvious index?
Date: Sun, 29 Aug 2004 19:09:54 -0700 (PDT)
Message-ID: <20040830020954.3596.qmail@web41110.mail.yahoo.com> (raw)
In-Reply-To: <87llfxk5v6.fsf@stark.xeocode.com>
--- Greg Stark <gsstark@mit.edu> wrote:
>
> Mr Pink <mr_pink_is_the_only_pro@yahoo.com> writes:
>
> > AFAIK postgres doesn't peek at values used in a query when optimizing
>
> Of course it does.
But not ones returned by a function such as now(), or when you use bind variables, as Tom aptly
explained.
That's what I meant by 'peek'. Interestingly enough Oracle does that, it's inline with their
policy of recommending the use of bind variables. Perhaps postgres could use such a feature some
day.
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
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: mr_pink_is_the_only_pro@yahoo.com
Subject: Re: Why does a simple query not use an obvious index?
In-Reply-To: <20040830020954.3596.qmail@web41110.mail.yahoo.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