@@ -124,7 +124,7 @@ SET pg_pathman.enable = t;</programlisting>
124124 ensure scalability, and optimize database administration processes
125125 you can use partitioning — splitting a large table into smaller
126126 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
128128 inheritance. Each partition is created as a child table with a
129129 CHECK constraint. For example:
130130 </para>
@@ -238,7 +238,7 @@ create_range_partitions(relation REGCLASS,
238238 attribute TEXT,
239239 start_value ANYELEMENT,
240240 p_interval ANYELEMENT | INTERVAL,
241- p_count INTEGER DEFAULT NULL
241+ p_count INTEGER DEFAULT NULL,
242242 partition_data BOOLEAN DEFAULT TRUE)
243243</programlisting>
244244 <para>
@@ -1033,14 +1033,14 @@ create_range_partitions(relation REGCLASS,
10331033 attribute TEXT,
10341034 start_value ANYELEMENT,
10351035 p_interval ANYELEMENT,
1036- count INTEGER DEFAULT NULL
1036+ p_count INTEGER DEFAULT NULL,
10371037 partition_data BOOLEAN DEFAULT TRUE)
10381038
10391039create_range_partitions(relation REGCLASS,
10401040 attribute TEXT,
10411041 start_value ANYELEMENT,
10421042 p_interval INTERVAL,
1043- count INTEGER DEFAULT NULL,
1043+ p_count INTEGER DEFAULT NULL,
10441044 partition_data BOOLEAN DEFAULT TRUE)
10451045</programlisting>
10461046 <para>