X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 056E9D1B92D for ; Wed, 20 Aug 2003 17:41:33 -0300 (ADT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 91050-07 for ; Wed, 20 Aug 2003 17:41:21 -0300 (ADT) Received: from mailav.tor1.inquent.com (mail.inquent.com [216.208.117.106]) by svr1.postgresql.org (Postfix) with ESMTP id EF23BD1B998 for ; Wed, 20 Aug 2003 17:41:18 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mailav.tor1.inquent.com (Postfix) with ESMTP id AB2B41024D; Wed, 20 Aug 2003 16:33:34 -0400 (EDT) Received: from [10.0.2.6] (unknown [10.0.2.6]) by mailav.tor1.inquent.com (Postfix) with ESMTP id BEC1E10248; Wed, 20 Aug 2003 16:33:32 -0400 (EDT) Subject: Re: "SELECT IN" Still Broken in 7.4b From: Rod Taylor To: Stephan Szabo Cc: Mike Winter , pgsql-sql@postgresql.org In-Reply-To: <20030820103841.Q10580-100000@megazone.bigpanda.com> References: <20030820103841.Q10580-100000@megazone.bigpanda.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-nDZ1+Iq0+cY2EgtxZXQN" Message-Id: <1061412091.40948.65.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Wed, 20 Aug 2003 20:41:32 +0000 X-Virus-Scanned: by AMaViS perl-11 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/244 X-Sequence-Number: 14860 --=-nDZ1+Iq0+cY2EgtxZXQN Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2003-08-20 at 17:41, Stephan Szabo wrote: > On Wed, 20 Aug 2003, Rod Taylor wrote: >=20 > > > Thanks, Stephan. I was really hoping that the IN(valuelist) was goin= g to > > > be changed at the same time, because it really is unusable for anythi= ng > > > over a couple of thousand values. > > > > Changed to do what? >=20 > One possibility might be to act as if the valuelist was a table and do the > IN as if it were that way, rather than treating it as a set of ORs. That > would be basically like doing the temporary table solution, but without > requiring the user to do it. 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. --=-nDZ1+Iq0+cY2EgtxZXQN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQA/Q9z76DETLow6vwwRAiiKAJ9ECh4k0KxBXet6GgCB2qWFo5HOJwCfYlMl Xn9AsCrUImT1TD6h0wJUjnQ= =w3rw -----END PGP SIGNATURE----- --=-nDZ1+Iq0+cY2EgtxZXQN--