From: Dani Oderbolz <oderbolz@ecologic.de>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: pgsql-sql@postgresql.org
Subject: Re: "SELECT IN" Still Broken in 7.4b
Date: Thu, 21 Aug 2003 12:05:14 +0200
Message-ID: <3F44995A.8040308@ecologic.de> (raw)
In-Reply-To: <20030820143116.S17177-100000@megazone.bigpanda.com>
References: <20030820143116.S17177-100000@megazone.bigpanda.com>
Stephan Szabo wrote:
>On Wed, 20 Aug 2003, Rod Taylor wrote:
>...
>
>
>>Is the temp table version any faster? I realize it has a higher limit
>>to the number of items you can have in the list.
>>
>>
>
>Within the scope of the new hashed IN stuff I believe so in at least some
>cases. I have a few million row table of integers where searching for
>values IN (~10000 values) takes longer than creating the temp table,
>copying into it and doing the in subquery. That's not a particularly
>meaningful test case, but sending the psql output to /dev/null gives me: ...
>
But where do your values come from in the first place?
Couldn't you optimize your model so that you don't have to copy around
such amounts of data?
Regards,
Dani
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-hackers@postgresql.org
Cc: oderbolz@ecologic.de, sszabo@megazone.bigpanda.com, pgsql-sql@postgresql.org
Subject: Re: "SELECT IN" Still Broken in 7.4b
In-Reply-To: <3F44995A.8040308@ecologic.de>
* 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