From: keithf4 (@keithf4) <noreply+keithf4@github.com>
To: pgpartman/pg_partman <noreply+pgpartman-pg_partman@github.com>
Subject: Re: [pgpartman/pg_partman] PR #884: [Request for Feedback] feature: Allow indexes to be created without attaching them to a parent
Date: Fri, 06 Nov 2026 16:55:59 +0000
Message-ID: <gh-pgpartman-pg_partman-884-c6690427701@github.com> (raw)
In-Reply-To: <gh-pgpartman-pg_partman-884@github.com>
References: <gh-pgpartman-pg_partman-884@github.com>
Going by your description, you're saying that indexes should only be made on the template. But that is definitely not a design pattern I want. The code looks like it tries to compare to see if the template index exists on the parent and only includes it if it does. Is that the intent?
I would only want this if it could support either the parent or the template having the indexes, not only the template. And not cause issues if someone did it on both, or clearly throw errors and detect it when it happens. I'd tried doing this before but ran into issues trying to find a foolproof way of deduping any possible index on the template vs the parent. So I went with only supporting primary/unique indexes on the template and the remaining ones on the parent table.
If that is the intent of this PR, I'll have to take time and check more carefully to see if that is what this is allowing.