pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Rowley <drowley@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Doc: clarify partitioned table limitations
Date: Mon, 05 Sep 2022 06:44:36 +0000
Message-ID: <E1oV5qV-001WE3-TP@gemulon.postgresql.org> (raw)

Doc: clarify partitioned table limitations

Improve documentation regarding the limitations of unique and primary key
constraints on partitioned tables.  The existing documentation didn't make
it clear that the constraint columns had to be present in the partition
key as bare columns.  The reader could be led to believe that it was ok to
include the constraint columns as part of a function call's parameters or
as part of an expression.  Additionally, the documentation didn't mention
anything about the fact that we disallow unique and primary key
constraints if the partition keys contain *any* function calls or
expressions, regardless of if the constraint columns appear as columns
elsewhere in the partition key.

The confusion here was highlighted by a report on the general mailing list
by James Vanns.

Discussion: https://postgr.es/m/CAH7vdhNF0EdYZz3GLpgE3RSJLwWLhEk7A_fiKS9dPBT3Dz_3eA@mail.gmail.com
Discussion: https://postgr.es/m/CAApHDvoU-u9iTqKjteYRFfi+UNEk7dbSAcyxEQD==vZt9B1KnA@mail.gmail.com
Reviewed-by: Erik Rijkers
Backpatch-through: 11

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/a254545a54a2e14ec6f41b8190d6c6713a85a18a

Modified Files
--------------
doc/src/sgml/ddl.sgml | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)



view thread (6+ messages)  latest in thread

Message-ID: <E1oV5qV-001WE3-TP@gemulon.postgresql.org>
Permalink:  ../E1oV5qV-001WE3-TP@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1oV5qV-001WE3-TP@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: drowley@postgresql.org
  Subject: Re: pgsql: Doc: clarify partitioned table limitations
  In-Reply-To: <E1oV5qV-001WE3-TP@gemulon.postgresql.org>
  References: <E1oV5qV-001WE3-TP@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox