Re: CLUSTER sort on abbreviated expressions is broken

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CLUSTER sort on abbreviated expressions is broken
Date: 2022-04-03 23:33:28
Message-ID: CA+hUKGK=4osGviPYciALX99jUm3Fp8moS0FxYkqxTMnMbJc-4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 4, 2022 at 11:12 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> We will need a backpatchable fix, since Thomas' recent fix (commit
> cc58eecc5d75a9329a6d49a25a6499aea7ee6fd6) only targeted the master
> branch.

I probably should have made it clearer in the commit message,
cc58eecc5 doesn't fix this problem in the master branch. It only
fixes the code that incorrectly assumed that datum1 was always
available. Now it skips the optimised path, and falls back to the
slow path, that still has *this* bug, and the test upthread still
fails. I wrote about this separately because it's clearly independent
and I didn't want it to be mistaken for an open item for 15.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2022-04-03 23:58:13 Re: unlogged sequences
Previous Message Peter Geoghegan 2022-04-03 23:11:51 Re: CLUSTER sort on abbreviated expressions is broken