Re: pgsql: pg_plan_advice: Add CHECK_FOR_INTERRUPTS() and check_stack_depth

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: pg_plan_advice: Add CHECK_FOR_INTERRUPTS() and check_stack_depth
Date: 2026-09-10 18:12:19
Message-ID: CA+TgmobnSd-VB-C5DgCpU9T0wotsOfNzB5eoUrJu_3Vop66zKw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Sep 10, 2026 at 1:41 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> On Wed, Sep 09, 2026 at 10:39:46PM +0000, Robert Haas wrote:
> > pg_plan_advice: Add CHECK_FOR_INTERRUPTS() and check_stack_depth()
>
> koel is unhappy with this one:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=koel&dt=2026-09-10%2010%3A34%3A01

Yeah, Bilal reported that to me earlier via Discord. Fix pushed now.
(I didn't see this email before pushing it.)

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2026-09-10 20:11:02 pgsql: Rename PqMsg_Progress to PqParallelMsg_Progress.
Previous Message Robert Haas 2026-09-10 18:06:14 pgsql: pg_plan_advice: Document interaction with GEQO.