@@ -154,7 +154,7 @@ nodes. It will help us run and observe PostgreSQL.
154154 " curl https://install.citusdata.com/community/deb.sh | sudo bash" \
155155 " sudo DEBIAN_FRONTEND=noninteractive apt-get install -q -y postgresql-common" \
156156 " echo 'create_main_cluster = false' | sudo tee -a /etc/postgresql-common/createcluster.conf" \
157- " sudo DEBIAN_FRONTEND=noninteractive apt-get install -q -y postgresql-11 -auto-failover-1.4 " \
157+ " sudo DEBIAN_FRONTEND=noninteractive apt-get install -q -y postgresql-16 -auto-failover" \
158158 " sudo usermod -a -G postgres ha-admin" &
159159 done
160160 wait
@@ -178,7 +178,7 @@ own roles in the system.
178178 --auth trust \
179179 --ssl-self-signed \
180180 --pgdata monitor \
181- --pgctl /usr/lib/postgresql/11 /bin/pg_ctl
181+ --pgctl /usr/lib/postgresql/16 /bin/pg_ctl
182182
183183 This command initializes a PostgreSQL cluster at the location pointed
184184by the ``--pgdata `` option. When ``--pgdata `` is omitted, ``pg_autoctl ``
@@ -225,7 +225,7 @@ We’ll create the primary database using the ``pg_autoctl create`` subcommand.
225225 --username ha-admin \
226226 --dbname appdb \
227227 --hostname ha-demo-a.internal.cloudapp.net \
228- --pgctl /usr/lib/postgresql/11 /bin/pg_ctl \
228+ --pgctl /usr/lib/postgresql/16 /bin/pg_ctl \
229229 --monitor 'postgres://autoctl_node@ha-demo-monitor.internal.cloudapp.net/pg_auto_failover?sslmode=require'
230230
231231Notice the user and database name in the monitor connection string -- these
@@ -274,7 +274,7 @@ Next connect to node B and do the same process. We'll do both steps at once:
274274 --username ha-admin \
275275 --dbname appdb \
276276 --hostname ha-demo-b.internal.cloudapp.net \
277- --pgctl /usr/lib/postgresql/11 /bin/pg_ctl \
277+ --pgctl /usr/lib/postgresql/16 /bin/pg_ctl \
278278 --monitor 'postgres://autoctl_node@ha-demo-monitor.internal.cloudapp.net/pg_auto_failover?sslmode=require'
279279
280280 ssh -T -l ha-admin ` vm_ip b` << CMD
0 commit comments