From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Improve documentation about PRIMARY KEY constraints. |
Date: | 2016-02-07 21:03:07 |
Message-ID: | E1aSWU7-0003hq-Fc@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Improve documentation about PRIMARY KEY constraints.
Get rid of the false implication that PRIMARY KEY is exactly equivalent to
UNIQUE + NOT NULL. That was more-or-less true at one time in our
implementation, but the standard doesn't say that, and we've grown various
features (many of them required by spec) that treat a pkey differently from
less-formal constraints. Per recent discussion on pgsql-general.
I failed to resist the temptation to do some other wordsmithing in the
same area.
Branch
------
REL9_3_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/abcb32d55ed8da8c158936d5a48a0c3b84bfe3ff
Modified Files
--------------
doc/src/sgml/ddl.sgml | 58 ++++++++++++++++++++------------------
doc/src/sgml/ref/create_table.sgml | 26 ++++++++---------
2 files changed, 44 insertions(+), 40 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-02-08 10:06:22 | pgsql: Fix overeager pushdown of HAVING clauses when grouping sets are |
Previous Message | Tom Lane | 2016-02-07 19:57:34 | pgsql: Fix deparsing of ON CONFLICT arbiter WHERE clauses. |