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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: feichanghong <feichanghong(at)qq(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Date: 2025-09-18 07:05:55
Message-ID: CAApHDvq79oXC6gLXvd_ktOUJ4CDWgcWNB+CKNe3MSdt3+jrkWg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 18 Sept 2025 at 18:20, Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> Oops, coffee deficiency. Updated again.

Thanks for updating the patch.

I think the original intent of "Parsed test spec with 3 sessions"
(from 759d9d676) was two sessions doing work, and an independent
observer session. Is there a reason to add 2 more sessions? Maybe it's
me not working with the isolation tester often enough, but I'd have
expected you to add steps for s1 and s2 then define permutations for
those steps.

David

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2025-09-18 08:25:28 Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Previous Message Amit Langote 2025-09-18 06:20:20 Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos