Re: Plan for update ... where a is not distinct from b

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Plan for update ... where a is not distinct from b
Date: 2017-11-28 14:35:33
Message-ID: 13950.1511879733@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Peter J. Holzer" <hjp-pgsql(at)hjp(dot)at> writes:
> I noticed that an update was taking a long time and found this:
> [ crappy plan for join on IS NOT DISTINCT ]

Yeah, there's no optimization smarts at all for IS [NOT] DISTINCT.
It can't be converted into a merge qual, nor a hash qual, nor an
indexscan qual.

In principle this could be improved, but given how much work it'd be
and how seldom anyone complains, it's not likely to happen anytime soon.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dilip Kumar 2017-11-28 14:45:09 Re: ERROR: too many dynamic shared memory segments
Previous Message Tom Lane 2017-11-28 14:25:47 Re: Refreshing materialized views