docs: import CloudNativePG main

Author: cnpg-bot

website/docs/quickstart.md

@@ -99,6 +99,11 @@ metadata:
 spec:
   instances: 3
 
+  postgresql:
+    synchronous:
+      method: any
+      number: 1
+
   storage:
     size: 1Gi
 ```

website/docs/replication.md

@@ -125,9 +125,12 @@ CloudNativePG supports both
     By default, synchronous replication pauses write operations if the required
     number of standby nodes for WAL replication during transaction commits is
     unavailable. This behavior prioritizes data durability and aligns with
-    PostgreSQL DBA best practices. However, if self-healing is a higher priority
+    PostgreSQL DBA best practices. As a general rule, plan for synchronous
+    replication in clusters with at least three instances, to tolerate the loss
+    of one of them. However, if self-healing is a higher priority
     than strict data durability in your setup, this setting can be adjusted. For
-    details on managing this behavior, refer to the [Data Durability and Synchronous Replication](#data-durability-and-synchronous-replication)
+    details on managing this behavior, refer to the
+    [Data Durability and Synchronous Replication](#data-durability-and-synchronous-replication)
     section.
 :::
 

website/docs/samples/cluster-example.yaml

@@ -4,7 +4,12 @@ metadata:
   name: cluster-example
 spec:
   instances: 3
-  
+
+  postgresql:
+    synchronous:
+      method: any
+      number: 1
+
   storage:
     size: 1Gi