Re: Optimising "in" queries - Mailing list pgsql-performance

From Michael Glaesemann
Subject Re: Optimising "in" queries
Date
Msg-id AAF53AEE-B98C-45BD-B80F-8FA528BFB98B@seespotcode.net
Whole thread Raw
In response to Re: Optimising "in" queries  (Russell Smith <mr-russ@pws.com.au>)
Responses Re: Optimising "in" queries  (Russell Smith <mr-russ@pws.com.au>)
Re: Optimising "in" queries  (Stephen Davies <scldad@sdc.com.au>)
List pgsql-performance
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



pgsql-performance by date:

Previous
From: Russell Smith
Date:
Subject: Re: Optimising "in" queries
Next
From: "Dmitry Potapov"
Date:
Subject: io storm on checkpoints, postgresql 8.2.4, linux