| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | jph(at)openjph(dot)be, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Table Partitioning |
| Date: | 2020-07-30 17:40:31 |
| Message-ID: | 20200730174031.GB16709@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Jul 30, 2020 at 01:33:29PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/ddl-partitioning.html
> Description:
>
> With version 12 using declarative partitioning request that the column used
> for patitioning is part of the PRIMARY KEY of the table as you can see in
> the error message below.
>
> ERROR: insufficient columns in PRIMARY KEY constraint definition
> DETAIL: PRIMARY KEY constraint on table "ztest" lacks column "mtime" which
> is part of the partition key.
>
> If I've well understood, this was not the case in previous versions, but it
> becomes mandatory in version 12 (and maybe 11 too). Such restriction is not
> mentioned in the documentation for version 12 and would be suitable to be.
Can you give us a reproducible test case?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-07-30 18:00:23 | Re: Table Partitioning |
| Previous Message | Bruce Momjian | 2020-07-30 15:41:17 | Re: High Availability, Load Balancing, and Replication Feature Matrix |