| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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 03:10:51 |
| Message-ID: | 18801.1562641851@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> Attached is an idea of patch for the documentation, using this
> wording:
> + <listitem>
> + <para>
> + When defining a primary key on a partitioned table, the primary
> + key column must be included in the partition key.
> + </para>
> + </listitem>
Isn't it the other way around, that the partition key column(s) must be
included in the primary key? Maybe I'm confused, but it seems like
we couldn't enforce PK uniqueness otherwise.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2019-07-09 03:12:18 | Re: Postgres 11: Table Partitioning and Primary Keys |
| Previous Message | Michael Paquier | 2019-07-09 02:58:56 | Re: Postgres 11: Table Partitioning and Primary Keys |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2019-07-09 03:12:18 | Re: Postgres 11: Table Partitioning and Primary Keys |
| Previous Message | Thomas Munro | 2019-07-09 03:04:27 | Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11 |