Re: BUG #19026: ResourceOwnerForget can't find owner for invalid plancache
Dilip Kumar <dilipbalaut@gmail.com>
From: Dilip Kumar <dilipbalaut@gmail.com>
To: exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2025-08-20T11:21:07Z
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 re-execution of a failed SQLFunctionCache entry.
- a67d4847a431 19 (unreleased) landed
- 906b68217a1e 18.0 landed
Attachments
- release_plan_on_error.patch (application/octet-stream) patch
On Wed, Aug 20, 2025 at 4:01 PM PG Bug reporting form <noreply@postgresql.org> wrote: > > The following bug has been logged on the website: > > Bug reference: 19026 > Logged by: Alexander Lakhin > Email address: exclusion@gmail.com > PostgreSQL version: 18beta3 > Operating system: Ubuntu 24.04 > Description: > > The following script: > create function part_hashint4_noop(value int4, seed int8) > returns int8 as $$ > create table t(); > select value + seed; > $$ language sql strict immutable parallel safe; > > create operator class part_test_int4_ops for type int4 using hash as > function 2 part_hashint4_noop(int4, int8); > > create table pt(i int) partition by hash (i part_test_int4_ops); > create table p1 partition of pt for values with (modulus 4, remainder 0); > > insert into pt values (1); > insert into pt values (1); > > triggers an expected error and then an internal one: > ERROR: CREATE TABLE is not allowed in a non-volatile function > CONTEXT: SQL function "part_hashint4_noop" statement 1 > > ERROR: XX000: plancache reference 0x643ae41a7d98 is not owned by resource > owner Portal > CONTEXT: SQL function "part_hashint4_noop" during startup > LOCATION: ResourceOwnerForget, resowner.c:618 The problem is in init_execution_state() we store the On error resource owner will be released, but that references are still maintained in the plan and cowner in fcache, but on error the transaction will be aborted and this resource owner will be released. So next time when we try to clean up, it will access invalid memory. So a simple fix would be to cleanup on error as attached POC. -- Regards, Dilip Kumar Google