agora inbox for [email protected]help / color / mirror / Atom feed
[PATCH 3/3] Listify a note on the CREATE TABLE page 35+ messages / 2 participants [nested] [flat]
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 82 ++++++++++++++++++++++---------------- 1 file changed, 47 insertions(+), 35 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..161f7d1280 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -262,41 +262,53 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI </para> <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> + <itemizedlist> + <listitem> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercable to the corresponding partition key column's type. + </para> + </listitem> + + <listitem> + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + </listitem> + + <listitem> + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + </listitem> + + <listitem> + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> + </listitem> + </itemizedlist> </note> <para> -- 2.11.0 --------------434C61868FD2E7C005F82712 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------434C61868FD2E7C005F82712-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH 3/3] Listify a note on the CREATE TABLE page @ 2017-02-27 10:00 amit <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: amit @ 2017-02-27 10:00 UTC (permalink / raw) --- doc/src/sgml/ref/create_table.sgml | 74 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index bb081ff86f..f08433c667 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI any existing partition of that parent. </para> - <note> - <para> - Each of the values specified in the partition bound specification is - a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. - A literal is either a numeric constant or a string constant that is - coercable to the corresponding partition key column's type. - </para> - - <para> - When creating a range partition, the lower bound specified with - <literal>FROM</literal> is an inclusive bound, whereas the upper bound - specified with <literal>TO</literal> is an exclusive bound. That is, - the values specified in the <literal>FROM</literal> list are accepted - values of the corresponding partition key columns in a given partition, - whereas those in the <literal>TO</literal> list are not. To be precise, - this applies only to the first of the partition key columns for which - the corresponding values in the <literal>FROM</literal> and - <literal>TO</literal> lists are not equal. All rows in a given - partition contain the same values for all preceding columns, equal to - those specified in <literal>FROM</literal> and <literal>TO</literal> - lists. On the other hand, any subsequent columns are insignificant - as far as implicit partition constraint is concerned. - - Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> - signifies <literal>-infinity</literal> as the lower bound of the - corresponding column, whereas it signifies <literal>+infinity</literal> - as the upper bound when specified in <literal>TO</literal>. - </para> - - <para> - When creating a list partition, <literal>NULL</literal> can be specified - to signify that the partition allows the partition key column to be null. - However, there cannot be more than one such list partitions for a given - parent table. <literal>NULL</literal> cannot specified for range - partitions. - </para> - </note> + <para> + Each of the values specified in the partition bound specification is + a literal, <literal>NULL</literal>, or <literal>UNBOUNDED</literal>. + A literal is either a numeric constant or a string constant that is + coercible to the corresponding partition key column's type. + </para> + + <para> + When creating a range partition, the lower bound specified with + <literal>FROM</literal> is an inclusive bound, whereas the upper + bound specified with <literal>TO</literal> is an exclusive bound. + That is, the values specified in the <literal>FROM</literal> list + are accepted values of the corresponding partition key columns in a + given partition, whereas those in the <literal>TO</literal> list are + not. To be precise, this applies only to the first of the partition + key columns for which the corresponding values in the <literal>FROM</literal> + and <literal>TO</literal> lists are not equal. All rows in a given + partition contain the same values for all preceding columns, equal to + those specified in <literal>FROM</literal> and <literal>TO</literal> + lists. On the other hand, any subsequent columns are insignificant + as far as implicit partition constraint is concerned. + </para> + + <para> + Specifying <literal>UNBOUNDED</literal> in <literal>FROM</literal> + signifies <literal>-infinity</literal> as the lower bound of the + corresponding column, whereas it signifies <literal>+infinity</literal> + as the upper bound when specified in <literal>TO</literal>. + </para> + + <para> + When creating a list partition, <literal>NULL</literal> can be + specified to signify that the partition allows the partition key + column to be null. However, there cannot be more than one such + list partitions for a given parent table. <literal>NULL</literal> + cannot specified for range partitions. + </para> <para> A partition must have the same column names and types as the partitioned -- 2.11.0 --------------19C79A137EF2D0DB3BE72F79 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers --------------19C79A137EF2D0DB3BE72F79-- ^ permalink raw reply [nested|flat] 35+ messages in thread
* [PATCH v25 8/9] Row pattern recognition patch (typedefs.list). @ 2024-12-21 06:19 Tatsuo Ishii <[email protected]> 0 siblings, 0 replies; 35+ messages in thread From: Tatsuo Ishii @ 2024-12-21 06:19 UTC (permalink / raw) --- src/tools/pgindent/typedefs.list | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/tools/pgindent/typedefs.list b/src/tools/pgindent/typedefs.list index 971a150dbb..bf78e162bc 100644 --- a/src/tools/pgindent/typedefs.list +++ b/src/tools/pgindent/typedefs.list @@ -1690,6 +1690,7 @@ NamedLWLockTrancheRequest NamedTuplestoreScan NamedTuplestoreScanState NamespaceInfo +NavigationInfo NestLoop NestLoopParam NestLoopState @@ -2316,6 +2317,9 @@ RI_CompareKey RI_ConstraintInfo RI_QueryHashEntry RI_QueryKey +RPCommonSyntax +RPSkipTo +RPSubsetItem RTEKind RTEPermissionInfo RWConflict @@ -2670,6 +2674,7 @@ SimpleStringList SimpleStringListCell SingleBoundSortItem Size +SkipContext SkipPages SlabBlock SlabContext @@ -2761,6 +2766,7 @@ StreamStopReason String StringInfo StringInfoData +StringSet StripnullState SubLink SubLinkType @@ -3085,6 +3091,7 @@ VarString VarStringSortSupport Variable VariableAssignHook +VariablePos VariableSetKind VariableSetStmt VariableShowStmt -- 2.25.1 ----Next_Part(Sat_Dec_21_18_20_04_2024_526)-- Content-Type: Text/X-Patch; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="v25-0009-Allow-to-print-raw-parse-tree.patch" ^ permalink raw reply [nested|flat] 35+ messages in thread
end of thread, other threads:[~2024-12-21 06:19 UTC | newest] Thread overview: 35+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2017-02-27 10:00 [PATCH 3/3] Listify a note on the CREATE TABLE page amit <[email protected]> 2024-12-21 06:19 [PATCH v25 8/9] Row pattern recognition patch (typedefs.list). Tatsuo Ishii <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox