Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Дата
Msg-id aKLPJet54cgC3JNA@paquier.xyz
обсуждение исходный текст
Ответ на Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c  (Masahiko Sawada <sawada.mshk@gmail.com>)
Ответы Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Список pgsql-bugs
On Fri, Aug 08, 2025 at 12:15:19AM -0700, Masahiko Sawada wrote:
> On Thu, Aug 7, 2025 at 4:39 PM Michael Paquier <michael@paquier.xyz> wrote:
> >
> > On Thu, Aug 07, 2025 at 10:29:41AM -0700, Masahiko Sawada wrote:
> > > Yes, it's definitely possible to create the test using isolation. I
> > > wasn't sure how to invoke isolation tests only when injection points
> > > are enabled.
> >
> > For meson, I think that I would tweak the isolation test list based on
> > get_option('injection_points'), and do a similar thing for Makefile.
>
> Thank you for the advice! I've changed the regression tests to use
> isolation tests.

That's enough to reproduce the MULL pointer dereference, thanks!

I would suggest to add a description at the top of foreign_recheck,
documenting the purpose of the test.

+# "s0_lock" execute a FOR UPDATE query but it stops before locking the result
s/execute/executes/, with an 's'.

Fujita-san, are you planning to look at the proposal?
--
Michael

Вложения

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