diff options
| author | Robert Haas <rhaas@postgresql.org> | 2017-05-18 13:48:10 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2017-05-18 13:49:31 -0400 |
| commit | 3ec76ff1f2cf52e9b900349957b42d28128b7bc7 (patch) | |
| tree | b7eef4bb3d490b31ec2d25f7067912d4ea9d20c4 /doc/src | |
| parent | 2df537e43fdc432cccbe64de166ac97363cbca3c (diff) | |
Don't explicitly mark range partitioning columns NOT NULL.
This seemed like a good idea originally because there's no way to mark
a range partition as accepting NULL, but that now seems more like a
current limitation than something we want to lock down for all time.
For example, there's a proposal to add the notion of a default
partition which accepts all rows not otherwise routed, which directly
conflicts with the idea that a range-partitioned table should never
allow nulls anywhere. So let's change this while we still can, by
putting the NOT NULL test into the partition constraint instead of
changing the column properties.
Amit Langote and Robert Haas, reviewed by Amit Kapila
Discussion: http://postgr.es/m/8e2dd63d-c6fb-bb74-3c2b-ed6d63629c9d@lab.ntt.co.jp
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/ref/create_table.sgml | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 484f81898b3..0478e40447d 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -454,11 +454,6 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI these constraints on individual partitions. </para> - <para> - When using range partitioning, a <literal>NOT NULL</literal> constraint - is added to each non-expression column in the partition key. - </para> - </listitem> </varlistentry> |