On 2019-Jan-10, Tom Lane wrote:
> > On 2019-Jan-10, PG Bug reporting form wrote:
> >> ALTER TABLE ONLY t1 ADD CONSTRAINT uniq_t1_i1_i2 UNIQUE (i1, i2);
> >> [ leads to ]
> >> Indexes:
> >> "uniq_t1_i1_i2" UNIQUE CONSTRAINT, btree (i1, i2) INVALID
> I concur that the code is operating as designed. I think however that
> there's a user-experience problem here, which is that INVALID suggests
> that something's broken. I wonder if we could improve matters by
> making psql and the docs describe this state of a partitioned index
> as INCOMPLETE.
Hmm, yeah, I can see how that can be confusing. Not sure of the
difficulty of a fix ... I'll have a think about it.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services