On Thu, 2024-12-19 at 11:09 -0500, Peter Geoghegan wrote:
> I should point out (for the benefit of Tom, or whoever writes the next
> set of release notes) that I think that this bug is very unlikely to
> occur in practice. Getting wrong answers to queries could only happen
> given an index with more than 3 columns, and only for scans with just
> the right combination of scan key types. It could also only happen
> when the scan advances its array keys using high keys with more than a
> single truncated attribute.
Just for the record: a customer just ran into this bug. REINDEX did
not fix the bad query result, but update to 17.3 did.
Yours,
Laurenz Albe
--
*E-Mail Disclaimer*
Der Inhalt dieser E-Mail ist ausschliesslich fuer den
bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat
dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte,
dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder
Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
*CONFIDENTIALITY NOTICE & DISCLAIMER
*This message and any attachment are
confidential and may be privileged or otherwise protected from disclosure
and solely for the use of the person(s) or entity to whom it is intended.
If you have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this message and
any attachment from your system. If you are not the intended recipient, be
advised that any use of this message is prohibited and may be unlawful, and
you must not copy this message or attachment or disclose the contents to
any other person.
