Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 71bb410

Browse files
author
Liudmila Mantrova
committed
DOC: sync multimaster install instructions between 9.6 and 10
1 parent 99d9c36 commit 71bb410

File tree

1 file changed

+14
-10
lines changed

1 file changed

+14
-10
lines changed

doc/src/sgml/multimaster.sgml

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -344,34 +344,38 @@
344344
<para>Suppose
345345
you are setting up a cluster of three nodes, with
346346
<literal>node1</literal>, <literal>node2</literal>, and
347-
<literal>node3</literal> domain names. First, set up the database to be replicated, and make sure you have a user with superuser rights to perform replication:
347+
<literal>node3</literal> domain names. First, set up the database to be replicated, and make sure you have a DBMS user with superuser rights to perform replication:
348348
</para>
349349
<itemizedlist>
350350
<listitem>
351351
<para>
352352
If you are starting from scratch, initialize a cluster,
353-
create an empty database <literal>mydb</literal> and a new
354-
user <literal>myuser</literal>, on each node of the cluster. For details, see <xref linkend="creating-cluster">.
353+
create an empty database <literal>mydb</literal> and a new DBMS
354+
user <literal>myuser</literal> with superuser rights, on each node of the cluster. For details, see <xref linkend="creating-cluster">.
355355
</para>
356356
</listitem>
357357
<listitem>
358358
<para>
359359
If you already have a database <literal>mydb</literal>
360-
running on <literal>node1</literal>, initialize
360+
running on <literal>node1</literal>, create a new DBMS user
361+
<literal>myuser</literal> with superuser rights and initialize
361362
new nodes from the working node using
362-
<application>pg_basebackup</application>. On behalf of <literal>myuser</literal>, run the following command on each node you are going to add:
363+
<application>pg_basebackup</application> on behalf of this user.
364+
Run the following command on each node you are going to add:
363365
<programlisting>
364-
pg_basebackup -D <replaceable>datadir</> -h node1 mydb
366+
pg_basebackup -D <replaceable>datadir</> -h node1 -U myuser mydb
365367
</programlisting>
366368
where <replaceable>datadir</> is the directory containing the database cluster. This directory is specified at the cluster initialization stage, or set in the <envar>PGDATA</envar> environment variable.
369+
You can also use any other DBMS user with superuser rights instead of <literal>myuser</literal> to perform this task.
367370
</para>
368371
<para>
369372
For details on using <application>pg_basebackup</application>, see
370373
<xref linkend="app-pgbasebackup">.
371374
</para>
372375
</listitem>
373376
</itemizedlist>
374-
<para>Once the database is set up, complete the following steps on each
377+
<para>Once the database is set up, complete the following steps on behalf
378+
of the <literal>postgres</literal> OS user, on each
375379
cluster node:
376380
</para>
377381
<orderedlist>
@@ -513,16 +517,16 @@ netstat -ln | grep -E '5432|5433'
513517
</listitem>
514518
<listitem>
515519
<para>
516-
Restart <productname>PostgreSQL</productname>:
520+
On behalf of an OS superuser, restart <productname>&productname;</productname>:
517521
</para>
518522
<programlisting>
519-
pg_ctl -D <replaceable>datadir</replaceable> -l <replaceable>pg.log</replaceable> start
523+
pg_ctl -D <replaceable>datadir</replaceable> -l <replaceable>pg.log</replaceable> restart
520524
</programlisting>
521525
</listitem>
522526
</orderedlist>
523527
<para>
524528
When <productname>&productname;</productname> is started on all nodes, connect to any node
525-
and create the <filename>multimaster</filename> extension:
529+
on behalf of the <literal>postgres</literal> OS user and create the <filename>multimaster</filename> extension:
526530
<programlisting>
527531
psql -h node1
528532
CREATE EXTENSION multimaster;</programlisting></para>

0 commit comments

Comments
 (0)