@@ -136,7 +136,7 @@ SET pg_pathman.enable = t;</programlisting>
136136 ensure scalability, and optimize database administration processes
137137 you can use partitioning — splitting a large table into smaller
138138 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
140140 inheritance. Each partition is created as a child table with a
141141 CHECK constraint. For example:
142142 </para>
@@ -250,7 +250,7 @@ create_range_partitions(relation REGCLASS,
250250 attribute TEXT,
251251 start_value ANYELEMENT,
252252 p_interval ANYELEMENT | INTERVAL,
253- p_count INTEGER DEFAULT NULL
253+ p_count INTEGER DEFAULT NULL,
254254 partition_data BOOLEAN DEFAULT TRUE)
255255</programlisting>
256256 <para>
@@ -988,14 +988,14 @@ create_range_partitions(relation REGCLASS,
988988 attribute TEXT,
989989 start_value ANYELEMENT,
990990 p_interval ANYELEMENT,
991- count
991+ p_count INTEGER DEFAULT NULL,
992992 partition_data BOOLEAN DEFAULT TRUE)
993993
994994create_range_partitions(relation REGCLASS,
995995 attribute TEXT,
996996 start_value ANYELEMENT,
997997 p_interval INTERVAL,
998- count INTEGER DEFAULT NULL,
998+ p_count INTEGER DEFAULT NULL,
999999 partition_data BOOLEAN DEFAULT TRUE)
10001000</programlisting>
10011001 <para>
