From: ritojoao (@ritojoao) <noreply+ritojoao@github.com>
To: pgpartman/pg_partman <noreply+pgpartman-pg_partman@github.com>
Subject: Re: [pgpartman/pg_partman] issue #870: Error while creating nested partition with pg_partman
Date: Thu, 19 Nov 2026 16:18:19 +0000
Message-ID: <gh-pgpartman-pg_partman-870-c7014952969@github.com> (raw)
In-Reply-To: <gh-pgpartman-pg_partman-870@github.com>
References: <gh-pgpartman-pg_partman-870@github.com>
Hi,
I tried both SQL scripts from this issue (the LIST -> RANGE case from the first post and the nested HASH -> RANGE case from the comment) on current master (5.5.1, commit e0a6c38). I ran them exactly as written, on PostgreSQL 17.12 and 16.16.
Both calls to `create_partition()` returned `t`, with no error:
- LIST -> RANGE (`public.events_standard`, premake 3, `p_constraint_cols => ARRAY['id']`): created 7 daily partitions plus the default.
- HASH -> RANGE (`public.events_p00`, premake 1, `p_constraint_cols => ARRAY['id']`): created 3 daily partitions plus the default.
The errors in the report came from 5.4.3. It looks like this was fixed after that release, possibly by the sub-partitioning fix in #857, but I did not bisect to confirm which commit. If the original reporter can retest on 5.5.1, this issue may be closable.
I only tested the two scripts above, not other nesting depths or partition types.