Re: Perfomance of IN-clause with many elements and possible solutions

From: Dmitry Lazurkin <dilaz03(at)gmail(dot)com>
To: PT <wmoran(at)potentialtech(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Perfomance of IN-clause with many elements and possible solutions
Date: 2017-07-24 21:56:43
Message-ID: 4912428a-6768-5f35-d39e-c3a62ae470df@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 25.07.2017 00:17, PT wrote:
> The IN clause is not what's taking all the time. It's the processing of
> millions of rows that's taking all the time.

IN (...) - 17 sec
IN (VALUES ...) - 4 sec
So performance issue is with IN-clause.

> Perhaps you should better describe what it is you really want to accomplish.
> Regardless of what it is, if it involves processing many millions of rows,
> you're probably going to need to do some sort of materialization.

I try to find better solutions for IN-task.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dmitry Lazurkin 2017-07-24 22:12:04 Re: Perfomance of IN-clause with many elements and possible solutions
Previous Message David G. Johnston 2017-07-24 21:31:53 Re: Perfomance of IN-clause with many elements and possible solutions