Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: David Rowley <dgrowleyml@gmail.com>

Cc: Amit Langote <amitlangote09@gmail.com>, feichanghong <feichanghong@qq.com>, pgsql-bugs@lists.postgresql.org

Date: 2025-09-18T04:38:19Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix EPQ crash from missing partition pruning state in EState
- 9a82a64edcd8 18.0 landed
- 8741e48e5dda 19 (unreleased) landed
Calculate agglevelsup correctly when Aggref contains a CTE.
- b0cc0a71e0a0 19 (unreleased) cited
Move PartitionPruneInfo out of plan nodes into PlannedStmt
- bb3ec16e14de 18.0 cited

David Rowley <dgrowleyml@gmail.com> writes:
> ... I don't
> think we need to put up signs anywhere that indicate mistakes once
> existed here, especially for ones that existed in no released version
> of PostgreSQL.

I'm a bit bemused by that viewpoint.  There's an enormous fraction of
our test suite that is exactly memorializing bugs that once existed.
Maybe there is some reason to distinguish bugs that never made it
into an official release, but that seems rather weak to me.

			regards, tom lane