Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com>
Cc: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
Subject: Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange
Date: 2021-06-22 13:42:18
Message-ID: 202106221342.lab2x5tvhcbs@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2021-Jun-22, Neil Chen wrote:

> Greetings,
>
> I tried to investigate the bug, but the complicated logic here completely
> messed up my mind...
>
> Anyway, this patch can fix it and make the regress test happy. But I think
> it's better to get the author's advice - I copied this email to Alvaro,
> hope it doesn't offend him...

Without looking too deeply, the patch seems sensible to me. However,
I'm CC'ing Alexander and Paul :-)

--
Álvaro Herrera Valdivia, Chile

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2021-06-22 13:46:16 Re: BUG #17068: Incorrect ordering of a particular row.
Previous Message David Rowley 2021-06-22 13:32:37 Re: BUG #17068: Incorrect ordering of a particular row.