Re: Checking = with timestamp field is slow

From: Michael Glaesemann <grzm(at)myrealbox(dot)com>
To: Antony Paul <antonypaul24(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Checking = with timestamp field is slow
Date: 2004-11-05 08:14:01
Message-ID: A64DEAC4-2F02-11D9-BE4A-000A95C88220@myrealbox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On Nov 5, 2004, at 4:16 PM, Antony Paul wrote:
> where today::date = '2004-11-05';
>
> This is the only condition in the query. There is a btree index on the
> column today.
> Is there any way to optimise it.

I'm sure others out there have better ideas, but you might want to try

where current_date = date '2004-11-05'

Might not make a difference at all, but perhaps PostgreSQL is coercing
both values to timestamp or some other type as you're only providing a
string to compare to a date. Then again, it might make no difference at
all.

My 1 cent.

Michael Glaesemann
grzm myrealbox com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Glaesemann 2004-11-05 08:32:49 Re: Checking = with timestamp field is slow
Previous Message Antony Paul 2004-11-05 07:16:20 Checking = with timestamp field is slow