Re: IN list processing performance (yet again)

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Dave Tenny <tenny(at)attbi(dot)com>
Cc: Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>, pgsql-performance(at)postgresql(dot)org
Subject: Re: IN list processing performance (yet again)
Date: 2003-05-28 18:41:50
Message-ID: 20030528184150.GB6118@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, May 28, 2003 at 13:58:14 -0400,
Dave Tenny <tenny(at)attbi(dot)com> wrote:
> A join isn't an option, these elements come a a selection of entity ID's
> that are specific to some client context.
> Some other people suggested joins too.

You can union the values together and then join (or use where exists) with the
result. This may not be faster and you may not be able to union several
thousand selects together in a single statement. But it shouldn't be too
much work to test it out.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dave Tenny 2003-05-28 19:57:22 Re: IN list processing performance (yet again)
Previous Message Bruno Wolff III 2003-05-28 18:39:14 Re: IN list processing performance (yet again)