From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Doc: improve partitioning discussion in ddl.sgml. |
Date: | 2020-11-14 18:10:17 |
Message-ID: | E1ke009-0004aJ-Rg@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Doc: improve partitioning discussion in ddl.sgml.
This started with the intent to explain that range upper bounds
are exclusive, which previously you could only find out by reading
the CREATE TABLE man page. But I soon found that section 5.11
really could stand a fair amount of editorial attention. It's
apparently been revised several times without much concern for
overall flow, nor careful copy-editing.
Back-patch to v11, which is as far as the patch goes easily.
Per gripe from Edson Richter. Thanks to David Johnston for review.
Discussion: https://postgr.es/m/DM6PR13MB3988736CF8F5DC5720440231CFE60@DM6PR13MB3988.namprd13.prod.outlook.com
Branch
------
REL_11_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/a87d7801c24ffb3593841838ba0e3d4883d34853
Modified Files
--------------
doc/src/sgml/ddl.sgml | 372 +++++++++++++++++++++++++++-----------------------
1 file changed, 203 insertions(+), 169 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-11-14 22:05:46 | pgsql: Provide the OR REPLACE option for CREATE TRIGGER. |
Previous Message | Michael Paquier | 2020-11-14 02:43:50 | pgsql: Fix some typos |