Re: [PG19] plpgsql: SELECT INTO sets FOUND wrongly after a function becomes a SRF

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PG19] plpgsql: SELECT INTO sets FOUND wrongly after a function becomes a SRF
Date: 2026-10-06 00:43:07
Message-ID: CAGRkXqR0fDG86srteCMNSPyVbsns61r_VbXEAOTBPEs_bEUcWw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Tom,
> is quite useless: we dealt with expr->plan == NULL a few lines
> earlier, so this if-test can never succeed. Pushed with that
> change.

Thanks for pushing, and for the quick look. Agreed on the plan check.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-10-06 01:00:12 Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers
Previous Message Masahiko Sawada 2026-10-06 00:36:08 Re: Parallel autovacuum: DROP DATABASE WITH (FORCE) fails on the parallel workers