Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit4785e37

Browse files
committed
Tidy up the CREATE TABLE documentation for partitioning.
Remove some <note> tags that make this too "loud". Fix some typos.Amit Langote, with a few minor corrections by meDiscussion:http://postgr.es/m/a6f99cdb-21e7-1d65-1381-91f2cfa156e2@lab.ntt.co.jp
1 parent7ecb714 commit4785e37

File tree

1 file changed

+37
-37
lines changed

1 file changed

+37
-37
lines changed

‎doc/src/sgml/ref/create_table.sgml

Lines changed: 37 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI
261261
any existing partition of that parent.
262262
</para>
263263

264-
<note>
265-
<para>
266-
Each of the values specified in the partition bound specification is
267-
a literal, <literal>NULL</literal>, or<literal>UNBOUNDED</literal>.
268-
A literal is either a numeric constant or a string constant that is
269-
coercable to the corresponding partition key column's type.
270-
</para>
271-
272-
<para>
273-
When creating a range partition,thelower bound specified with
274-
<literal>FROM</literal> is aninclusive bound, whereas the upper bound
275-
specifiedwith<literal>TO</literal>is an exclusive bound. That is,
276-
the valuesspecified inthe<literal>FROM</literal> list are accepted
277-
values of the correspondingpartition key columns ina given partition,
278-
whereas those in the <literal>TO</literal> list are not. To be precise,
279-
this applies only tothefirst ofthepartition key columns for which
280-
the corresponding values in the<literal>FROM</literal>and
281-
<literal>TO</literal> lists are not equal. All rows in a given
282-
partition contain the same values for all preceding columns, equal to
283-
those specified in <literal>FROM</literal> and <literal>TO</literal>
284-
lists. On the other hand, any subsequent columns are insignificant
285-
as far as implicit partition constraint is concerned.
286-
287-
Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal>
288-
signifies<literal>-infinity</literal>as the lower bound of the
289-
corresponding column, whereas itsignifies <literal>+infinity</literal>
290-
as the upper bound when specified in<literal>TO</literal>.
291-
</para>
292-
293-
<para>
294-
When creating a list partition, <literal>NULL</literal> can be specified
295-
to signify that thepartition allows the partition key column to be null.
296-
However, there cannot be more than one such list partitions for a given
297-
parent table.<literal>NULL</literal>cannotspecified for range
298-
partitions.
299-
</para>
300-
</note>
264+
<para>
265+
Each of the values specified in the partition bound specification is
266+
a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>.
267+
A literal is either a numeric constant ora string constant that is
268+
coercible to the corresponding partition key column's type.
269+
</para>
270+
271+
<para>
272+
When creating a range partition, the lower bound specified with
273+
<literal>FROM</literal> is an inclusive bound, whereastheupper
274+
bound specified with<literal>TO</literal> is anexclusive bound.
275+
That is, the valuesspecifiedin the<literal>FROM</literal>list
276+
are accepted valuesofthecorresponding partition key columns in a
277+
givenpartition, whereas those inthe <literal>TO</literal> list are
278+
not. To be precise, this applies only to the first of the partition
279+
key columns for whichthecorresponding values inthe<literal>FROM</literal>
280+
and<literal>TO</literal>lists are not equal. All rows in a given
281+
partition contain the same values for all preceding columns, equal to
282+
those specified in <literal>FROM</literal> and <literal>TO</literal>
283+
lists. On the other hand, any subsequent columns are insignificant
284+
as far as implicit partition constraint is concerned.
285+
</para>
286+
287+
<para>
288+
Specifying<literal>UNBOUNDED</literal>in <literal>FROM</literal>
289+
signifies <literal>-infinity</literal> as the lower bound of the
290+
corresponding column, whereas it signifies<literal>+infinity</literal>
291+
as the upper bound when specified in <literal>TO</literal>.
292+
</para>
293+
294+
<para>
295+
When creating a listpartition, <literal>NULL</literal> can be
296+
specified to signify that the partition allows the partition key
297+
column to be null.However, therecannotbe more than one such
298+
list partition for a given parent table. <literal>NULL</literal>
299+
cannot be specified for range partitions.
300+
</para>
301301

302302
<para>
303303
A partition must have the same column names and types as the partitioned

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp