Re: Select in subselect vs select = any array

From: "mark" <dvlhntr(at)gmail(dot)com>
To: "'Adam Tistler'" <atistler(at)gmail(dot)com>, "'Pavel Stehule'" <pavel(dot)stehule(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Select in subselect vs select = any array
Date: 2011-03-22 02:55:11
Message-ID: 01fa01cbe83c$90b146d0$b213d470$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


> -----Original Message-----
> From: pgsql-performance-owner(at)postgresql(dot)org [mailto:pgsql-performance-
> owner(at)postgresql(dot)org] On Behalf Of Adam Tistler
> Sent: Monday, March 21, 2011 12:17 AM
> To: Pavel Stehule
> Cc: pgsql-performance(at)postgresql(dot)org
> Subject: Re: [PERFORM] Select in subselect vs select = any array
>
> Pavel, thanks for the help.
>
> I increased work_mem from 16MB to 64MB, no difference. The queries are
> really just a test case. My actual queries are actual just large
> number of primary keys that I am selecting from the db:
>
> For example:
> select * from nodes where node_id in ( 1, 2, 3 ..... )
>

What does "large" number of primary keys mean ?

I have seen some "odd" things happen when I passed, carelessly, tens of
thousands of items to an in list for a generated query, but I don't get the
feeling that isn't the case here.

..: Mark

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Merlin Moncure 2011-03-22 13:54:15 Re: Request for feedback on hardware for a new database server
Previous Message Scott Marlowe 2011-03-22 02:48:34 Re: REINDEX takes half a day (and still not complete!)