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 b31525c2-b22a-a810-3a12-b3667515753a@gmail.com
Whole thread Raw
In response to Re: [GENERAL] Perfomance of IN-clause with many elements and possible solutions  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: [GENERAL] Perfomance of IN-clause with many elements and possible solutions  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
On 31.07.2017 19:42, Jeff Janes wrote:
I think it is simply because no one has gotten around to implementing it that way.  When you can just write it as a values list instead, the incentive to make the regular in-list work better is not all that strong.

Cheers,

Jeff

I see from explain that IN-clause uses just array with function ANY. I think for efficient implementation of this task I should implement new datatype "hashset". Am I wrong?

pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [GENERAL] Perfomance of IN-clause with many elements and possible solutions
Next
From: "Peter J. Holzer"
Date:
Subject: Re: [GENERAL] Dealing with ordered hierarchies