Re: BUG #19484: Segmentation fault triggered by FDW

amit <amitlangote09@gmail.com>

From: Amit Langote <amitlangote09@gmail.com>
To: Matheus Alcantara <matheusssilv97@gmail.com>
Cc: Ayush Tiwari <ayushtiwari.slg01@gmail.com>, Rafia Sabih <rafia.pghackers@gmail.com>, 798604270@qq.com, pgsql-bugs@lists.postgresql.org, Etsuro Fujita <etsuro.fujita@gmail.com>, Amit Langote <amitlan@postgresql.org>
Date: 2026-06-10T13:09:12Z
Lists: pgsql-bugs
Hi Matheus,

On Wed, Jun 10, 2026 at 8:09 PM Matheus Alcantara
<matheusssilv97@gmail.com> wrote:
>
> On Wed Jun 10, 2026 at 2:15 AM -03, Ayush Tiwari wrote:
> >> One minor naming observation: the new fdwPrivLists field in
> >> ModifyTableState doesn't follow the mt_ prefix convention used by the
> >> other re-indexed lists (mt_updateColnosLists, mt_mergeActionLists,
> >> mt_mergeJoinConditions). Should we rename it to mt_fdwPrivLists for
> >> consistency?
> >>
> >
> > I think yes, it makes sense to rename it.
> >
>
> Attached v2 renamed, thanks.
>
> (Also CC Amit on this since he committed cbc127917e0 which I believe
> that is when the issue started)

Thanks for adding me.  I'll take a look at this early next week.

-- 
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