Re: unique indexes on partitioned tables

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: unique indexes on partitioned tables
Date: 2018-01-26 18:42:17
Message-ID: f974273b-50e6-b916-fb59-cbb1d057793f@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/22/18 17:55, Alvaro Herrera wrote:
> Alvaro Herrera wrote:
>> Version 4 of this patch, rebased on today's master.

+ if (key->partattrs[i] == 0)
+ ereport(ERROR,
+ (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
+ errmsg("unsupported %s constraint with
partition key definition",
+ constraint_type),
+ errmsg("%s constraints cannot be used when
partition keys include expressions.",
+ constraint_type)));

Double errmsg(). (Maybe an Assert somewhere should help catch this?)

+alter table idxpart add primary key (a); -- not an incomplete one tho

"though"?

I would like to see some tests that the unique constraints are actually
enforced. That is, insert some duplicate values and see it fail. Throw
some null values in, to check PK behavior as well. It should be
trivial, but seems kind of useful.

Other than that, this looks pretty good to me. A logical extension of
the previous partitioned index patch.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2018-01-26 18:57:54 Re: \describe*
Previous Message Stephen Frost 2018-01-26 18:35:19 Re: [HACKERS] Patch: Add --no-comments to skip COMMENTs with pg_dump