@@ -4142,21 +4142,21 @@ ALTER INDEX measurement_city_id_logdate_key
41424142 <orderedlist spacing="compact">
41434143 <listitem>
41444144 <para>
4145- Create the <quote>master </quote> table, from which all of the
4145+ Create the <quote>root </quote> table, from which all of the
41464146 <quote>child</quote> tables will inherit. This table will contain no data. Do not
41474147 define any check constraints on this table, unless you intend them
41484148 to be applied equally to all child tables. There is no point in
41494149 defining any indexes or unique constraints on it, either. For our
4150- example, themaster table is the <structname>measurement</structname>
4150+ example, theroot table is the <structname>measurement</structname>
41514151 table as originally defined.
41524152 </para>
41534153 </listitem>
41544154
41554155 <listitem>
41564156 <para>
41574157 Create several <quote>child</quote> tables that each inherit from
4158- themaster table. Normally, these tables will not add any columns
4159- to the set inherited from themaster . Just as with declarative
4158+ theroot table. Normally, these tables will not add any columns
4159+ to the set inherited from theroot . Just as with declarative
41604160 partitioning, these tables are in every way normal
41614161 <productname>PostgreSQL</productname> tables (or foreign tables).
41624162 </para>
@@ -4244,7 +4244,7 @@ CREATE INDEX measurement_y2008m01_logdate ON measurement_y2008m01 (logdate);
42444244 We want our application to be able to say <literal>INSERT INTO
42454245 measurement ...</literal> and have the data be redirected into the
42464246 appropriate child table. We can arrange that by attaching
4247- a suitable trigger function to themaster table.
4247+ a suitable trigger function to theroot table.
42484248 If data will be added only to the latest child, we can
42494249 use a very simple trigger function:
42504250
@@ -4326,7 +4326,7 @@ LANGUAGE plpgsql;
43264326 <para>
43274327 A different approach to redirecting inserts into the appropriate
43284328 child table is to set up rules, instead of a trigger, on the
4329- master table. For example:
4329+ root table. For example:
43304330
43314331<programlisting>
43324332CREATE RULE measurement_insert_y2006m02 AS
@@ -4351,15 +4351,15 @@ DO INSTEAD
43514351 <para>
43524352 Be aware that <command>COPY</command> ignores rules. If you want to
43534353 use <command>COPY</command> to insert data, you'll need to copy into the
4354- correct child table rather than directly into themaster . <command>COPY</command>
4354+ correct child table rather than directly into theroot . <command>COPY</command>
43554355 does fire triggers, so you can use it normally if you use the trigger
43564356 approach.
43574357 </para>
43584358
43594359 <para>
43604360 Another disadvantage of the rule approach is that there is no simple
43614361 way to force an error if the set of rules doesn't cover the insertion
4362- date; the data will silently go into themaster table instead.
4362+ date; the data will silently go into theroot table instead.
43634363 </para>
43644364 </listitem>
43654365
@@ -4473,7 +4473,7 @@ ALTER TABLE measurement_y2008m02 INHERIT measurement;
44734473<programlisting>
44744474ANALYZE measurement;
44754475</programlisting>
4476- will only process themaster table.
4476+ will only process theroot table.
44774477 </para>
44784478 </listitem>
44794479