From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | jph(at)openjph(dot)be, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Table Partitioning |
Date: | 2020-07-30 18:00:23 |
Message-ID: | 1546464.1596132023@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Jul 30, 2020 at 01:33:29PM +0000, PG Doc comments form wrote:
>> 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?
I don't think this is correct at all. The facility for pkeys or unique
constraints on partitioned tables simply didn't exist before v11:
$ psql
psql (10.13)
Type "help" for help.
postgres=# create table p(f1 int primary key, f2 int) partition by list(f2);
ERROR: primary key constraints are not supported on partitioned tables
LINE 1: create table p(f1 int primary key, f2 int) partition by list...
^
postgres=# create table p(f1 int unique, f2 int) partition by list(f2);
ERROR: unique constraints are not supported on partitioned tables
LINE 1: create table p(f1 int unique, f2 int) partition by list(f2);
^
so the fact that they're restricted in this way as of v11 and up
does not represent any loss of functionality.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2020-07-30 22:31:49 | 7 decimal digits precision for real |
Previous Message | Bruce Momjian | 2020-07-30 17:40:31 | Re: Table Partitioning |