| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Dmitry Lazurkin <dilaz03(at)gmail(dot)com> |
| Cc: | Bill Moran <wmoran(at)potentialtech(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Perfomance of IN-clause with many elements and possible solutions |
| Date: | 2017-07-31 17:08:47 |
| Message-ID: | CAMkU=1wtsMaN-g_ytLGO+PMQO9TLgVhR2VaGtuZGCACFBg+84A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jul 25, 2017 at 2:03 AM, Dmitry Lazurkin <dilaz03(at)gmail(dot)com> wrote:
> On 25.07.2017 05:50, Jeff Janes wrote:
>
>> It isn't either-or. It is the processing of millions of rows over the
>> large in-list which is taking the time. Processing an in-list as a hash
>> table would be great, but no one has gotten around to it implementing it
>> yet. Maybe Dmitry will be the one to do that.
>>
>
> Thanks. Yes, I want. But... Is this task too complex for novice?
>
Yes, it is probably too complex for a novice. On the other hand, you might
not be a novice anymore once you complete it!
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed Behn | 2017-07-31 17:52:29 | Partitioned TEMP tables |
| Previous Message | Jeff Janes | 2017-07-31 16:42:50 | Re: Perfomance of IN-clause with many elements and possible solutions |