Re: pg15.3: dereference null *plan in CachedPlanIsSimplyValid/plpgsql
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2023-07-20T15:55:32Z
Lists: pgsql-hackers
Justin Pryzby <pryzby@telsasoft.com> writes:
> A production instance crashed like so.
Oh, interesting. Apparently we got past the "Has cache invalidation fired
on this plan?" check:
if (!plansource->is_valid || plan != plansource->gplan || !plan->is_valid)
return false;
because "plan" and "plansource->gplan" were *both* null, which is
a case the code wasn't expecting. plansource.c seems to be paranoid
about gplan possibly being null everywhere else but here :-(
> Note that the prior query seems to have timed out in the same / similar plpgsql
> statement:
Hm. Perhaps that helps explain how we got into this state. It must
be some weird race condition, given the lack of prior reports.
Anyway, adding a check for plan not being null seems like the
obvious fix.
regards, tom lane
Commits
-
Guard against null plan pointer in CachedPlanIsSimplyValid().
- fbaf65cd65f4 15.4 landed
- c0f53139611c 16.0 landed
- 9089287aa037 17.0 landed
- 291c0254025b 13.12 landed
- 10fd061bbc66 14.9 landed