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

Поиск
Список
Период
Сортировка
От Amit Langote
Тема Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Дата
Msg-id CA+HiwqG7Heq9WuzwtNixdqYEOAgcEgmx7dQGkGE0Bwt3v0EBXw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos  (David Rowley <dgrowleyml@gmail.com>)
Ответы Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Список pgsql-bugs
On Thu, Sep 18, 2025 at 7:32 AM David Rowley <dgrowleyml@gmail.com> wrote:
> On Thu, 18 Sept 2025 at 09:43, David Rowley <dgrowleyml@gmail.com> wrote:
> > The first bad commit is:
> >
> > commit bb3ec16e14ded1d23a46d3c7e623a965164fa124
> > Author: Amit Langote <amitlan@postgresql.org>
> > Date:   Thu Jan 30 11:57:32 2025 +0900
> >
> >     Move PartitionPruneInfo out of plan nodes into PlannedStmt
>
> I think the attached is the correct fix.  I also wonder if it's worth
> an isolation test to exercise this code.

Thanks for the patch, David, and for the report, Fei.  I indeed forgot
to update EvalPlanQualStart() in that commit.

I agree about adding an isolation test, which I have done in the
attached updated patch.

--
Thanks, Amit Langote

Вложения

В списке pgsql-bugs по дате отправления: