Re: BUG #19484: Segmentation fault triggered by FDW

amit <amitlangote09@gmail.com>

From: Amit Langote <amitlangote09@gmail.com>
To: Etsuro Fujita <etsuro.fujita@gmail.com>
Cc: Richard Guo <guofenglinux@gmail.com>, Matheus Alcantara <matheusssilv97@gmail.com>, Ayush Tiwari <ayushtiwari.slg01@gmail.com>, Rafia Sabih <rafia.pghackers@gmail.com>, 798604270@qq.com, pgsql-bugs@lists.postgresql.org, Amit Langote <amitlan@postgresql.org>
Date: 2026-06-25T11:47:22Z
Lists: pgsql-bugs
Fujita-san,

On Thu, Jun 25, 2026 at 3:15 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> On Thu, Jun 25, 2026 at 8:24 AM Amit Langote <amitlangote09@gmail.com> wrote:
> > On Thu, Jun 25, 2026 at 2:02 AM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> > > This might be nitpicking, but:
> > >
> > > +           if (list_length(node->resultRelations) == mtstate->mt_nrels)
> > > +               fdw_private = (List *) list_nth(node->fdwPrivLists, j);
> > > +           else
> > > +           {
> > > +               Index       rti = resultRelInfo->ri_RangeTableIndex;
> > > +               ListCell   *lc1;
> > > +               ListCell   *lc2;
> > > +
> > > +               fdw_private = NIL;
> > > +               forboth(lc1, node->resultRelations, lc2, node->fdwPrivLists)
> > > +               {
> > > +                   if (lfirst_int(lc1) == (int) rti)
> > > +                   {
> > > +                       fdw_private = (List *) lfirst(lc2);
> > > +                       break;
> > > +                   }
> > > +               }
> > > +           }
> > >
> > > I'd put the if-test outside of the outer loop to save cycles.
> >
> > Right, it's loop-invariant. v3 attached computes a boolean
> > (nopruning), like labeltargets, once before the loop and uses it
> > inside.
> >
> > > Other than that v2 looks good to me.
> > >
> > > (The forboth loop actually causes an n-squared calculation, but it's
> > > done only when pruning occurs, in which case the number of remaining
> > > result relations would be reduced, so that wouldn't be a problem.)
> >
> > Right, though strictly the inner forboth scans node->resultRelations,
> > which pruning leaves at its original length, so it's the original
> > relation count that bounds the scan rather than the reduced one.
> > Either way it's EXPLAIN-only with small counts, so it's not a concern.
>
> That's right.
>
> The v3 patch looks good to me.  Thanks for updating the patch!

Pushed, thanks for checking.

-- 
Thanks, Amit Langote



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Avoid ABI break in ModifyTableState from the FDW pruning fix

  2. Re-index ModifyTable FDW arrays when pruning result relations

  3. Fix universal builds on MacOS

  4. Track unpruned relids to avoid processing pruned relations