@@ -136,7 +136,7 @@ SET pg_pathman.enable = t;</programlisting>
136
136
ensure scalability, and optimize database administration processes
137
137
you can use partitioning — splitting a large table into smaller
138
138
pieces, with each row moved to a single partition according to the
139
- partitioning key. <productname>PostgreSQL </productname> supports partitioning via table
139
+ partitioning key. <productname>&productname; </productname> supports partitioning via table
140
140
inheritance. Each partition is created as a child table with a
141
141
CHECK constraint. For example:
142
142
</para>
@@ -250,7 +250,7 @@ create_range_partitions(relation REGCLASS,
250
250
attribute TEXT,
251
251
start_value ANYELEMENT,
252
252
p_interval ANYELEMENT | INTERVAL,
253
- p_count INTEGER DEFAULT NULL
253
+ p_count INTEGER DEFAULT NULL,
254
254
partition_data BOOLEAN DEFAULT TRUE)
255
255
</programlisting>
256
256
<para>
@@ -988,14 +988,14 @@ create_range_partitions(relation REGCLASS,
988
988
attribute TEXT,
989
989
start_value ANYELEMENT,
990
990
p_interval ANYELEMENT,
991
- count INTEGER DEFAULT NULL
991
+ p_count INTEGER DEFAULT NULL,
992
992
partition_data BOOLEAN DEFAULT TRUE)
993
993
994
994
create_range_partitions(relation REGCLASS,
995
995
attribute TEXT,
996
996
start_value ANYELEMENT,
997
997
p_interval INTERVAL,
998
- count INTEGER DEFAULT NULL,
998
+ p_count INTEGER DEFAULT NULL,
999
999
partition_data BOOLEAN DEFAULT TRUE)
1000
1000
</programlisting>
1001
1001
<para>
0 commit comments