Re: [GENERAL] Perfomance of IN-clause with many elements and possiblesolutions - Mailing list pgsql-general

From Dmitry Lazurkin
Subject Re: [GENERAL] Perfomance of IN-clause with many elements and possiblesolutions
Date
Msg-id 4912428a-6768-5f35-d39e-c3a62ae470df@gmail.com
Whole thread Raw
In response to Re: [GENERAL] Perfomance of IN-clause with many elements andpossible solutions  (PT <wmoran@potentialtech.com>)
List 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.


pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: [GENERAL] Perfomance of IN-clause with many elements and possible solutions
Next
From: Dmitry Lazurkin
Date:
Subject: Re: [GENERAL] Perfomance of IN-clause with many elements and possiblesolutions