Re: Incremental Sort crash on a rescan that becomes bounded

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(at)vondra(dot)me>, jtc331(at)gmail(dot)com
Subject: Re: Incremental Sort crash on a rescan that becomes bounded
Date: 2026-11-18 02:37:51
Message-ID: CAApHDvr_CZ5hiqiv-TuxLfUDdLRCESX89Q94DGUuNdsQwJhGPA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 17 Nov 2026 at 05:21, shihao zhong <zhong950419(at)gmail(dot)com> wrote:
> > Maybe in master we could adjust the tuplesort_reset()
> > function to take the allowbounded parameter.
>
> I think we should do that.

I've done that in master only

> I tested V2 locally and it looks good.

... and pushed the fix to all supported branches.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Haibo Yan 2026-11-18 02:35:19 Re: [PATCH v1] pg_stash_advice: Reject embedded NUL bytes in persistence files