From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | phil(dot)bayer(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postgres 11: Table Partitioning and Primary Keys |
Date: | 2019-07-09 02:37:37 |
Message-ID: | 20190709023737.vhrd4pxe4hgnd3ks@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Fri, Jul 5, 2019 at 09:20:07PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/ddl-partitioning.html
> Description:
>
> In the documentation for Postgres 11 table partitioning, there is no mention
> of the requirement that the Primary Key of a partitioned table must contain
> the partition key.
> In fact the documentation on primary keys is so light that I am not even
> 100% sure the above is correct. If the following table is not possible in
> Postgres 11, the documentation should find some way to make that clear.
>
> -- Create partitioned table with partition key not in primary key
> create table events (
> id bigint not null default nextval('events_id_seq'),
> created_date timestamp not null,
> constraint events_pk primary key (id)
> ) partition by range (created_date);
> -- end create table
>
> I believe this should be documented in section "5.10.2.3. Limitations"
Can someone comment on this? CC to hackers.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-07-09 02:58:56 | Re: Postgres 11: Table Partitioning and Primary Keys |
Previous Message | Jonathan S. Katz | 2019-07-08 21:51:25 | Re: TOC: List of Figures |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-07-09 02:45:47 | Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11 |
Previous Message | Thomas Munro | 2019-07-09 02:30:51 | Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11 |