From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: jesper.pedersen@redhat.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT
Date: Tue, 15 Jan 2019 15:26:28 -0300
Message-ID: <201901151826.bdqajmm7p3jk@alvherre.pgsql> (raw)
In-Reply-To: <3055.1547142109@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, jesper.pedersen@redhat.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT
In-Reply-To: <201901151826.bdqajmm7p3jk@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox