| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| 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:12:18 |
| Message-ID: | CAKFQuwZfzNGTTo4zVn0Q=wfXujfaKdFbn7v5eAp20Eud7r95cA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Mon, Jul 8, 2019 at 7:59 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> 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>
> If somebody has any better idea for that paragraph, please feel free.
>
Reads a bit backward. How about:
"As uniqueness can only be enforced within an individual partition when
defining a primary key on a partitioned table all columns present in the
partition key must also exist in the primary key."
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-07-09 03:32:34 | Re: Ambiguous language in Table 8.13. Special Date/Time Inputs |
| Previous Message | Tom Lane | 2019-07-09 03:10:51 | Re: Postgres 11: Table Partitioning and Primary Keys |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-07-09 03:26:33 | Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11 |
| Previous Message | Tom Lane | 2019-07-09 03:10:51 | Re: Postgres 11: Table Partitioning and Primary Keys |