From: Michael Glaesemann <grzm@seespotcode.net>
To: Russell Smith <mr-russ@pws.com.au>
Cc: Stephen Davies <scldad@sdc.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: Optimising "in" queries
Date: Wed, 22 Aug 2007 08:25:26 -0500
Message-ID: <AAF53AEE-B98C-45BD-B80F-8FA528BFB98B@seespotcode.net> (raw)
In-Reply-To: <46CC16F3.7060606@pws.com.au>
References: <200708221210.36770.scldad@sdc.com.au>
<46CC16F3.7060606@pws.com.au>
On Aug 22, 2007, at 5:58 , Russell Smith wrote:
> Stephen Davies wrote:
>> select count(rdate),rdate from reading where sensor_id in
>> (1137,1138,1139,1140) group by rdate order by rdate desc limit 1;
>>
>>
> It would have been helpful to see the table definition here. I can
> say up front that array processing in postgres is SLOW.
Um, what array processing are you seeing here? IN (a, b, b) is not an
array construct.
Michael Glaesemann
grzm seespotcode net
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: grzm@seespotcode.net, mr-russ@pws.com.au, scldad@sdc.com.au
Subject: Re: Optimising "in" queries
In-Reply-To: <AAF53AEE-B98C-45BD-B80F-8FA528BFB98B@seespotcode.net>
* 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