pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Kuzmenkov <a.kuzmenkov@postgrespro.ru>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Uninterruptible long planning of a query with too many WHERE clauses
Date: Mon, 12 Nov 2018 11:21:10 -0500
Message-ID: <5156.1542039670@sss.pgh.pa.us> (raw)
In-Reply-To: <37b95215-b315-ecbc-0747-037ac48ad4c4@postgrespro.ru>
References: <90c5bdfa-d633-dabe-9889-3cf3e1acd443@postgrespro.ru>
	<21010.1541911093@sss.pgh.pa.us>
	<37b95215-b315-ecbc-0747-037ac48ad4c4@postgrespro.ru>

Alexander Kuzmenkov <a.kuzmenkov@postgrespro.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




view thread (4+ messages)

Message-ID: <5156.1542039670@sss.pgh.pa.us>
Permalink:  ../5156.1542039670@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/5156.1542039670@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, a.kuzmenkov@postgrespro.ru
  Subject: Re: Uninterruptible long planning of a query with too many WHERE clauses
  In-Reply-To: <5156.1542039670@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox