| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, phil(dot)bayer(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postgres 11: Table Partitioning and Primary Keys |
| Date: | 2019-07-09 06:51:40 |
| Message-ID: | 20190709065140.GB17321@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Tue, Jul 09, 2019 at 03:34:48PM +0900, Michael Paquier wrote:
> Looking closely at the code in DefineIndex() (and as Rajkumar has
> mentioned upthread for unique constraints) this can happen for primary
> keys, unique constraints and exclusion constraints. So we had better
> mention all three of them. I am not sure that we need to be explicit
> about the uniqueness part though, let's say the following:
> "When defining a primary key, a unique constraint or an exclusion
> constraint on a partitioned table, all the columns present in the
> constraint definition must be included in the partition key."
Let's try again that (that's a long day..):
"When defining a primary key, a unique constraint or an exclusion
constraint on a partitioned table, all the columns present in the
partition key must be included in the constraint definition."
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2019-07-09 06:59:32 | Re: Postgres 11: Table Partitioning and Primary Keys |
| Previous Message | Michael Paquier | 2019-07-09 06:49:24 | Re: Postgres 11: Table Partitioning and Primary Keys |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2019-07-09 06:59:32 | Re: Postgres 11: Table Partitioning and Primary Keys |
| Previous Message | Michael Paquier | 2019-07-09 06:49:24 | Re: Postgres 11: Table Partitioning and Primary Keys |