From: Joe Conway <mail@joeconway.com>
To: Mike Winter <mike.winter@frontlogic.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: "SELECT IN" Still Broken in 7.4b
Date: Wed, 20 Aug 2003 12:24:33 -0700
Message-ID: <3F43CAF1.9050405@joeconway.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0308201247550.6023-100000@frontlogic.com>
References: <Pine.LNX.4.33L2.0308201247550.6023-100000@frontlogic.com>
Mike Winter wrote:
> On Wed, 20 Aug 2003, Rod Taylor wrote:
>
>>Ensure your IN list is unique. You might find better times by through
>>an indexed temp table.
>
> That is what I ended up doing, but it's not a very elegant solution.
> MySQL does queries of this type orders of magnitudes faster than Postgres
> on large value lists, although I have no specific algorithmic solutions to
> offer for how to make it faster. I don't believe making the IN lists
> unique has any affect on performance.
>
I have no idea whether it will be better or worse performance, but in
7.4 you could do:
select blah from foo where id = any (ARRAY[list_of_literals]);
Joe
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-sql@postgresql.org
Cc: mail@joeconway.com, mike.winter@frontlogic.com
Subject: Re: "SELECT IN" Still Broken in 7.4b
In-Reply-To: <3F43CAF1.9050405@joeconway.com>
* 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