phan2410 · July 16, 2025 09:52 · Feb 25, 2024 · Feb 24, 2024 · Feb 4, 2024 · Feb 4, 2024
diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -43,4 +43,9 @@ postgresql:
 3. Apply the YAML and wait for all nodes to restart
 4. Connect to the database using generated SuperUser secret (use kubectl proxy to forward the connection)
 5. Run `ALTER DATABASE template1 REFRESH COLLATION VERSION;`
-6. Optionally disable SuperUser if there's no need for it
+6. Run these two commands on ALL of the databases in the cluster:
+```
+REINDEX DATABASE <db_name>;
+ALTER DATABASE <db_name> REFRESH COLLATION VERSION;
+```
+7. Optionally disable SuperUser if there's no need for it
diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -29,8 +29,8 @@ postgresql:
 3. Find out on which node the first pod is running, ssh into it and `cd` into the dir which holds the pgdata volume (`/var/lib/rancher/k3s/storage/pvc-*/pgdata`)
 4. Inside pgdata volume edit `postgresql.conf`:
 
-- change pg_hba path from `/var/lib/postgresql/15/main/pg_hba.conf` to `/var/lib/postgresql/data/pgdata/pg_hba.conf`
-- change pg_ident path from `/var/lib/postgresql/15/main/pg_ident.conf` to `/var/lib/postgresql/data/pgdata/pg_ident.conf`
+- change `hba_file` path from `/var/lib/postgresql/15/main/pg_hba.conf` to `/var/lib/postgresql/data/pgdata/pg_hba.conf`
+- change `ident_file` path from `/var/lib/postgresql/15/main/pg_ident.conf` to `/var/lib/postgresql/data/pgdata/pg_ident.conf`
 - add `include 'custom.conf'` at the end of the file
 - add `include 'override.conf'` at the end of the file
 

diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -26,7 +26,7 @@ postgresql:
 
 1. Configure cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
 2. After starting the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
-3. Find out on which node the first pod is running, ssh into it and `cd` into the dir which holds the pgdata volume
+3. Find out on which node the first pod is running, ssh into it and `cd` into the dir which holds the pgdata volume (`/var/lib/rancher/k3s/storage/pvc-*/pgdata`)
 4. Inside pgdata volume edit `postgresql.conf`:
 
 - change pg_hba path from `/var/lib/postgresql/15/main/pg_hba.conf` to `/var/lib/postgresql/data/pgdata/pg_hba.conf`

diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -7,12 +7,13 @@
 - Empty files called `custom.conf` and `override.conf` inside pgdata folder on all nodes (folder where `postgresql.conf` is)
 - User named strictly `streaming_replica` with REPLICATION ROLE attached (if it's not `streaming_replica` cnpg will fail because it needs that user to exist)
 - Patroni dynamic config:
+
 ```yaml
 postgresql:
   parameters:
-    listen: '*'
+    listen: "*"
     max_wal_senders: 5
-    unix_socket_directories: '/controller/run'
+    unix_socket_directories: "/controller/run"
   pg_hba:
     - host replication replicator 127.0.0.1/32 md5
     # ...other lines for patroni replication...
@@ -23,21 +24,23 @@ postgresql:
 
 ## Creating cloudnative-pg cluster in replica mode
 
-1) Configure cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
-2) After starting the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
-3) Find out on which node the first pod is running, ssh into it and `cd` into the dir which holds the pgdata volume
-4) Inside pgdata volume edit `postgresql.conf`:
-  - change pg_hba path from `/var/lib/postgresql/15/main/pg_hba.conf` to `/var/lib/postgresql/data/pgdata/pg_hba.conf`
-  - change pg_ident path from `/var/lib/postgresql/15/main/pg_ident.conf` to `/var/lib/postgresql/data/pgdata/pg_ident.conf`
-  - add `include 'custom.conf'` at the end of the file
-  - add `include 'override.conf'` at the end of the file
-5) Restart the pod and it should start up correctly, after it all of the other pods will replicate from the first one as well
+1. Configure cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
+2. After starting the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
+3. Find out on which node the first pod is running, ssh into it and `cd` into the dir which holds the pgdata volume
+4. Inside pgdata volume edit `postgresql.conf`:
+
+- change pg_hba path from `/var/lib/postgresql/15/main/pg_hba.conf` to `/var/lib/postgresql/data/pgdata/pg_hba.conf`
+- change pg_ident path from `/var/lib/postgresql/15/main/pg_ident.conf` to `/var/lib/postgresql/data/pgdata/pg_ident.conf`
+- add `include 'custom.conf'` at the end of the file
+- add `include 'override.conf'` at the end of the file
+
+5. Restart the pod and it should start up correctly, after it all of the other pods will replicate from the first one as well
 
 ## Using the new cnpg-cluster
 
-1) Disable replica mode
-2) Enable SuperUser access
-3) Apply the YAML and wait for all nodes to restart
-4) Connect to the database using generated SuperUser secret (use kubectl proxy to forward the connection)
-5) Run `ALTER DATABASE template1 REFRESH COLLATION VERSION;`
-6) Optionally disable SuperUser if there's no need for it
+1. Disable replica mode
+2. Enable SuperUser access
+3. Apply the YAML and wait for all nodes to restart
+4. Connect to the database using generated SuperUser secret (use kubectl proxy to forward the connection)
+5. Run `ALTER DATABASE template1 REFRESH COLLATION VERSION;`
+6. Optionally disable SuperUser if there's no need for it
diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -21,7 +21,7 @@ postgresql:
     - host all all 0.0.0.0/0 md5
 ```
 
-## Creating cloudnative-pg cluster
+## Creating cloudnative-pg cluster in replica mode
 
 1) Configure cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
 2) After starting the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
@@ -31,4 +31,13 @@ postgresql:
   - change pg_ident path from `/var/lib/postgresql/15/main/pg_ident.conf` to `/var/lib/postgresql/data/pgdata/pg_ident.conf`
   - add `include 'custom.conf'` at the end of the file
   - add `include 'override.conf'` at the end of the file
-5) Restart the pod and it should start up correctly, after it all of the other pods will replicate from the first one as well
+5) Restart the pod and it should start up correctly, after it all of the other pods will replicate from the first one as well
+
+## Using the new cnpg-cluster
+
+1) Disable replica mode
+2) Enable SuperUser access
+3) Apply the YAML and wait for all nodes to restart
+4) Connect to the database using generated SuperUser secret (use kubectl proxy to forward the connection)
+5) Run `ALTER DATABASE template1 REFRESH COLLATION VERSION;`
+6) Optionally disable SuperUser if there's no need for it
diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -3,6 +3,7 @@
 ## Prerequisites
 
 - Stable connection to Patroni cluster from cnpg nodes
+- Same major PostgreSQL version (for example 15.1, cnpg image tag needs to correspond to that)
 - Empty files called `custom.conf` and `override.conf` inside pgdata folder on all nodes (folder where `postgresql.conf` is)
 - User named strictly `streaming_replica` with REPLICATION ROLE attached (if it's not `streaming_replica` cnpg will fail because it needs that user to exist)
 - Patroni dynamic config:

diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -24,7 +24,7 @@ postgresql:
 
 1) Configure cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
 2) After starting the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
-3) Find on which node the first pod is starting, ssh into it and `cd` into the dir which holds the pgdata volume
+3) Find out on which node the first pod is running, ssh into it and `cd` into the dir which holds the pgdata volume
 4) Inside pgdata volume edit `postgresql.conf`:
   - change pg_hba path from `/var/lib/postgresql/15/main/pg_hba.conf` to `/var/lib/postgresql/data/pgdata/pg_hba.conf`
   - change pg_ident path from `/var/lib/postgresql/15/main/pg_ident.conf` to `/var/lib/postgresql/data/pgdata/pg_ident.conf`

diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -23,7 +23,7 @@ postgresql:
 ## Creating cloudnative-pg cluster
 
 1) Configure cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
-2) After started the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
+2) After starting the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
 3) Find on which node the first pod is starting, ssh into it and `cd` into the dir which holds the pgdata volume
 4) Inside pgdata volume edit `postgresql.conf`:
   - change pg_hba path from `/var/lib/postgresql/15/main/pg_hba.conf` to `/var/lib/postgresql/data/pgdata/pg_hba.conf`

diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -22,7 +22,7 @@ postgresql:
 
 ## Creating cloudnative-pg cluster
 
-1) Configupre cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
+1) Configure cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
 2) After started the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
 3) Find on which node the first pod is starting, ssh into it and `cd` into the dir which holds the pgdata volume
 4) Inside pgdata volume edit `postgresql.conf`:

diff --git a/patronitocnpg.md b/patronitocnpg.md
@@ -0,0 +1,33 @@
+# Migrate Patroni PostgreSQL cluster to cloudnative-pg
+
+## Prerequisites
+
+- Stable connection to Patroni cluster from cnpg nodes
+- Empty files called `custom.conf` and `override.conf` inside pgdata folder on all nodes (folder where `postgresql.conf` is)
+- User named strictly `streaming_replica` with REPLICATION ROLE attached (if it's not `streaming_replica` cnpg will fail because it needs that user to exist)
+- Patroni dynamic config:
+```yaml
+postgresql:
+  parameters:
+    listen: '*'
+    max_wal_senders: 5
+    unix_socket_directories: '/controller/run'
+  pg_hba:
+    - host replication replicator 127.0.0.1/32 md5
+    # ...other lines for patroni replication...
+    - host replication streaming_replica 0.0.0.0/0 md5
+    - host all all 127.0.0.1/32 md5
+    - host all all 0.0.0.0/0 md5
+```
+
+## Creating cloudnative-pg cluster
+
+1) Configupre cnpg cluster to connect to Patroni via pgbasebackup and use that source-db as bootstrap and replica mode
+2) After started the cluster in replica mode, first init pod should succeed but afterwards the first cnpg pod will fail to start
+3) Find on which node the first pod is starting, ssh into it and `cd` into the dir which holds the pgdata volume
+4) Inside pgdata volume edit `postgresql.conf`:
+  - change pg_hba path from `/var/lib/postgresql/15/main/pg_hba.conf` to `/var/lib/postgresql/data/pgdata/pg_hba.conf`
+  - change pg_ident path from `/var/lib/postgresql/15/main/pg_ident.conf` to `/var/lib/postgresql/data/pgdata/pg_ident.conf`
+  - add `include 'custom.conf'` at the end of the file
+  - add `include 'override.conf'` at the end of the file
+5) Restart the pod and it should start up correctly, after it all of the other pods will replicate from the first one as well