Date: Thu, 21 Aug 2003 11:38:41 +0400 (MSD)
From: Oleg Bartunov <oleg@sai.msu.su>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Rod Taylor <rbt@rbt.ca>,
	Mike Winter <mike.winter@frontlogic.com>, pgsql-sql@postgresql.org
Subject: Re: "SELECT IN" Still Broken in 7.4b
In-Reply-To: <20030820103841.Q10580-100000@megazone.bigpanda.com>
Message-ID: <Pine.GSO.4.56.0308211137460.28800@ra.sai.msu.su>
References: <20030820103841.Q10580-100000@megazone.bigpanda.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 20 Aug 2003, Stephan Szabo wrote:

>
> On Wed, 20 Aug 2003, Rod Taylor wrote:
>
> > > Thanks, Stephan.  I was really hoping that the IN(valuelist) was going to
> > > be changed at the same time, because it really is unusable for anything
> > > over a couple of thousand values.
> >
> > Changed to do what?
>
> 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.
>

for integers we use contrib/intarray as a workaround. In principle,
it's possible to extend intarray to general array.

>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>

	Regards,
		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83