Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
Date: 2023-09-05 04:58:30
Message-ID: ZPa1drOinT9fv3CB@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Sep 04, 2023 at 05:00:00PM +0300, Alexander Lakhin wrote:
> 04.09.2023 09:35, Michael Paquier wrote:
>> It's also not something I would
>> backpatch. That's confusing, for sure, but there is also the argument
>> of keeping a consistent output in the stable branches.
>
> I agree. Let's not backpatch it.

Applied on HEAD, then. This item is now completely closed.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Lepikhov Andrei 2023-09-05 05:31:18 EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery
Previous Message Michael Paquier 2023-09-05 04:13:16 Re: BUG #17928: Standby fails to decode WAL on termination of primary