Re: BUG #19484: Segmentation fault triggered by FDW
Matheus Alcantara <matheusssilv97@gmail.com>
From: "Matheus Alcantara" <matheusssilv97@gmail.com>
To: "Ayush Tiwari" <ayushtiwari.slg01@gmail.com>
Cc: "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-10T11:08:56Z
Lists: pgsql-bugs
Attachments
- v2-0001-Re-index-ModifyTable-FDW-arrays-when-pruning-resu.patch (text/plain) patch v2-0001
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) -- Matheus Alcantara EDB: https://www.enterprisedb.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Avoid ABI break in ModifyTableState from the FDW pruning fix
- bba4e095d250 18 (unreleased) landed
-
Re-index ModifyTable FDW arrays when pruning result relations
- b43f8aa4cb30 19 (unreleased) landed
- 1ef917e3a61a 18 (unreleased) landed
-
Fix universal builds on MacOS
- 901ed9b352b4 19 (unreleased) cited
-
Track unpruned relids to avoid processing pruned relations
- cbc127917e04 18.0 cited