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

Commit e3da325

Browse files
author
Liudmila Mantrova
committed
DOC: bug fixes in shardman docs
1 parent 27abf8d commit e3da325

File tree

1 file changed

+1
-10
lines changed

1 file changed

+1
-10
lines changed

doc/src/sgml/pg_shardman.sgml

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -276,15 +276,6 @@
276276
a transaction confirmation until it is committed on all replicas.
277277
</para>
278278

279-
<important>
280-
<para>
281-
The <varname>shardman.sync_replication</varname> configuration variable should
282-
not be changed once the cluster is set up. If you would like to change
283-
the selected replication strategy, you have to remove all replicas
284-
and reconfigure the replication settings.
285-
</para>
286-
</important>
287-
288279
<para>
289280
By default, cluster redundancy level is 0, so replicas are not created.
290281
You can change the redundancy level as follows:
@@ -799,7 +790,7 @@ SELECT create_hash_partitions('films', 'id', 30, redundancy = 1);
799790
shards and replicas automatically. There is no easy way to define
800791
an index on the already sharded table, since the index must be created
801792
separately for each partition, as described in
802-
<ulink url="https://github.com/postgrespro/pg_pathman/wiki/How-do-I-create-indexes"><filename>pg_pathman wiki</filename></ulink>. To execute the same statement on all nodes,
793+
<ulink url="https://github.com/postgrespro/pg_pathman/wiki/How-do-I-create-indexes">pg_pathman wiki</ulink>. To execute the same statement on all nodes,
803794
you can use the <xref linkend="shardman-forall"> function.
804795
</para>
805796

0 commit comments

Comments
 (0)