Re: Uninterruptible long planning of a query with too many WHERE clauses

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Kuzmenkov <a(dot)kuzmenkov(at)postgrespro(dot)ru>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Uninterruptible long planning of a query with too many WHERE clauses
Date: 2018-11-12 16:21:10
Message-ID: 5156.1542039670@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alexander Kuzmenkov <a(dot)kuzmenkov(at)postgrespro(dot)ru> writes:
> El 11/11/18 a las 07:38, Tom Lane escribió:
>> I think you have the right basic idea, but we don't have to completely
>> lobotomize the bitmap-and search logic in order to cope with this.
>> This code is only trying to figure out which paths are potentially
>> redundant, so for a path with too many quals, we can just deem it
>> not-redundant, as attached.

> Thanks for the patch, looks good to me.

Pushed, thanks for reviewing.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-11-12 16:33:04 Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation
Previous Message Alvaro Herrera 2018-11-12 16:19:31 Re: Removal of unnecessary CommandCounterIncrement() when doing ON COMMIT DELETE ROWS