@@ -124,7 +124,7 @@ SET pg_pathman.enable = t;</programlisting>
124
124
ensure scalability, and optimize database administration processes
125
125
you can use partitioning — splitting a large table into smaller
126
126
pieces, with each row moved to a single partition according to the
127
- partitioning key. <productname>PostgreSQL </productname> supports partitioning via table
127
+ partitioning key. <productname>&productname; </productname> supports partitioning via table
128
128
inheritance. Each partition is created as a child table with a
129
129
CHECK constraint. For example:
130
130
</para>
@@ -238,7 +238,7 @@ create_range_partitions(relation REGCLASS,
238
238
attribute TEXT,
239
239
start_value ANYELEMENT,
240
240
p_interval ANYELEMENT | INTERVAL,
241
- p_count INTEGER DEFAULT NULL
241
+ p_count INTEGER DEFAULT NULL,
242
242
partition_data BOOLEAN DEFAULT TRUE)
243
243
</programlisting>
244
244
<para>
@@ -1033,14 +1033,14 @@ create_range_partitions(relation REGCLASS,
1033
1033
attribute TEXT,
1034
1034
start_value ANYELEMENT,
1035
1035
p_interval ANYELEMENT,
1036
- count INTEGER DEFAULT NULL
1036
+ p_count INTEGER DEFAULT NULL,
1037
1037
partition_data BOOLEAN DEFAULT TRUE)
1038
1038
1039
1039
create_range_partitions(relation REGCLASS,
1040
1040
attribute TEXT,
1041
1041
start_value ANYELEMENT,
1042
1042
p_interval INTERVAL,
1043
- count INTEGER DEFAULT NULL,
1043
+ p_count INTEGER DEFAULT NULL,
1044
1044
partition_data BOOLEAN DEFAULT TRUE)
1045
1045
</programlisting>
1046
1046
<para>
0 commit comments