pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: clarify that CREATE TABLE discards redundant unique constra
Date: 2020-12-08 18:10:16
Message-ID: E1kmhRI-0001QQ-QF@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Doc: clarify that CREATE TABLE discards redundant unique constraints.

The SQL standard says that redundant unique constraints are disallowed,
but we long ago decided that throwing an error would be too
user-unfriendly, so we just drop redundant ones. The docs weren't very
clear about that though, as this behavior was only explained for PRIMARY
KEY vs UNIQUE, not UNIQUE vs UNIQUE.

While here, I couldn't resist doing some copy-editing and markup-fixing
on the adjacent text about INCLUDE options.

Per bug #16767 from Matthias vd Meent.

Discussion: https://postgr.es/m/16767-1714a2056ca516d0@postgresql.org

Branch
------
REL_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/567d6d1ff6173cae02a4b89b4283137bf56caf97

Modified Files
--------------
doc/src/sgml/ref/create_table.sgml | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Dean Rasheed 2020-12-08 19:43:05 pgsql: Improve estimation of OR clauses using multiple extended statist
Previous Message Tom Lane 2020-12-08 17:06:38 pgsql: Doc: explain that the string types can't store \0 (ASCII NUL).