Re: ERROR: insufficient columns in the PRIMARY KEY constraint definition
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
Nagaraj Raj <nagaraj.sf@yahoo.com>,
Pg Bugs <pgsql-bugs@postgresql.org>
Date: 2020-09-29T23:21:30Z
Lists: pgsql-bugs
David Rowley <dgrowleyml@gmail.com> writes: > On Wed, 30 Sep 2020 at 12:08, David Rowley <dgrowleyml@gmail.com> wrote: >> Alvaro Herrera <alvherre@2ndquadrant.com> writes: >>> "Unique constraints (and[, by extension,] primary key constraints) on >>> partitioned tables must include all the partition key columns. > I didn't go with the same wording. The reason was that I didn't feel > the word "constraint" had to be mentioned twice. > I won't object if you or Alvaro want to keep Alvaro's suggestion though. I kind of like Alvaro's wording because it helps to reinforce the point that pkeys are a type of unique constraint. If you dislike repeating "constraints", perhaps we could go with something like Unique constraints (and hence primary keys) on partitioned tables ... I'm not hugely against your wording though. regards, tom lane
Commits
-
Reword partitioning error message
- f669ba7bdb00 12.5 landed
- 9fc212271289 14.0 landed
- 5b76e8fb675e 11.10 landed
- 49433744ff65 13.1 landed
-
Doc: Improve clarity on partitioned table limitations
- ab0c9c073563 11.10 landed
- 5c7afb4a29aa 12.5 landed
- 5610ffaf00a5 13.1 landed
- 2b888647d864 14.0 landed