Merge pull request #5548 from EnterpriseDB/pgd/replace_epas15v

PGD docs: Replacing epas 15 mentions with epas 16

product_docs/docs/pgd/5/admin-tpa/installing.mdx

@@ -62,7 +62,7 @@ For example:
 [tpa]$ tpaexec configure ~/clusters/speedy \
          --architecture PGD-Always-ON \
          --platform aws \
-         --edb-postgres-advanced 15 \
+         --edb-postgres-advanced 16 \
          --redwood \
          --location-names eu-west-1 eu-north-1 eu-central-1 \
          --data-nodes-per-location 3 \
@@ -76,7 +76,7 @@ The command creates a directory named `~/clusters/speedy` and generates a config
 In the example, the options select: 
 
 -  An AWS deployment (`--platform aws`) 
--  EDB Postgres Advanced Server, version 15 and Oracle compatibility (`--edb-postgres-advanced 15` and `--redwood`) 
+-  EDB Postgres Advanced Server, version 16 and Oracle compatibility (`--edb-postgres-advanced 16` and `--redwood`) 
 -  Three locations (`--location-names eu-west-1 eu-north-1 eu-central-1`) 
 -  Three data nodes at each location (`--data-nodes-per-location 3`) 
 -  Proxy routing policy of global (`--pgd-proxy-routing global`)

product_docs/docs/pgd/5/quickstart/connecting_applications.mdx

@@ -144,7 +144,7 @@ After you install `psql` or a similar client, you can connect to the cluster. Ru
 ```shell
 psql -h <ipaddressofnode> -p 6432 -U enterprisedb bdrdb
 __OUTPUT__
-psql (15.2, server 15.2.0 (Debian 15.2.0-2.buster))
+psql (16.2, server 16.2.0)
 SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits: 256, compression: off)
 Type "help" for help.
 
@@ -161,7 +161,7 @@ By listing all the addresses of proxies as the host, you can ensure that the cli
 ```shell
 psql -h <ipaddressofnode1>,<ipaddressofnode2>,<ipaddressofnode3> -U enterprisedb -p 6432 bdrdb
 __OUTPUT__
-psql (15.2, server 15.2.0 (Debian 15.2.0-2.buster))
+psql (16.2, server 16.2.0)
 SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits: 256, compression: off)
 Type "help" for help.
 

product_docs/docs/pgd/5/quickstart/further_explore_failover.mdx

@@ -134,7 +134,7 @@ If you want to be sure that this table is replicated, you can connect to another
 You'll see a login message similar to this:
 
 ```console
-psql.bin (15.2.0 (Debian 15.2.0-2.buster), server 15.2.0 (Debian 15.2.0-2.buster)) SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off) 
+psql.bin (16.2.0, server 16.2.0) SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off) 
 You are now connected to database "bdrdb" as user "enterprisedb" on host "kaftan" (address "10.33.25.233") at port "5444".
 bdrdb=#
 ```

product_docs/docs/pgd/5/quickstart/quick_start_aws.mdx

@@ -139,7 +139,7 @@ tpaexec configure democluster \
   --architecture PGD-Always-ON \
   --platform aws \
   --region eu-west-1 \
-  --edb-postgres-advanced 15 \
+  --edb-postgres-advanced 16 \
   --redwood \
   --location-names dc1 \
   --pgd-proxy-routing local \
@@ -164,7 +164,7 @@ By default, TPA configures Debian as the default OS for all nodes on AWS.
 
     Observe that you don't have to deploy PGD to the same platform you're using to run TPA!
 
-Specify that the data nodes will be running [EDB Postgres Advanced Server v15](/epas/latest/) (`--edb-postgres-advanced 15`) with Oracle compatibility (`--redwood`). 
+Specify that the data nodes will be running [EDB Postgres Advanced Server v16](/epas/latest/) (`--edb-postgres-advanced 16`) with Oracle compatibility (`--redwood`). 
 
 You set the notional location of the nodes to `dc1` using `--location-names`. You then set `--pgd-proxy-routing` to `local` so that proxy routing can route traffic to all nodes within each location.
 
@@ -250,7 +250,7 @@ You can now run the `psql` command to access the bdrdb database:
 ```shell
 psql bdrdb
 __OUTPUT__
-psql (15.2.0, server 15.2.0)
+psql (16.2.0, server 16.2.0)
 Type "help" for help.
 
 bdrdb=#
@@ -309,7 +309,7 @@ The proxies provide high-availability connections to the cluster of data nodes f
 ```shell
 psql -h kaboom,kaftan,kaolin -p 6432 bdrdb
 __OUTPUT__
-psql (15.2.0, server 15.2.0)
+psql (16.2.0, server 16.2.0)
 SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off)
 Type "help" for help.
 

product_docs/docs/pgd/5/quickstart/quick_start_docker.mdx

@@ -171,7 +171,7 @@ Run the [`tpaexec configure`](/tpa/latest/tpaexec-configure/) command to generat
 tpaexec configure democluster \
   --architecture PGD-Always-ON \
   --platform docker \
-  --edb-postgres-advanced 15 \
+  --edb-postgres-advanced 16 \
   --redwood \
   --location-names dc1 \
   --pgd-proxy-routing local \
@@ -194,7 +194,7 @@ Linux as the default image for all nodes.
 
     Observe that you don't have to deploy PGD to the same platform you're using to run TPA!
 
-Specify that the data nodes will be running [EDB Postgres Advanced Server v15](/epas/latest/) (`--edb-postgres-advanced 15`) with Oracle compatibility (`--redwood`). 
+Specify that the data nodes will be running [EDB Postgres Advanced Server v16](/epas/latest/) (`--edb-postgres-advanced 16`) with Oracle compatibility (`--redwood`). 
 
 You set the notional location of the nodes to `dc1` using `--location-names`. You then set `--pgd-proxy-routing` to `local` so that proxy routing can route traffic to all nodes within each location.
 
@@ -275,7 +275,7 @@ You can now run the `psql` command to access the `bdrdb` database:
 ```shell
 psql bdrdb
 __OUTPUT__
-psql (15.2.0, server 15.2.0)
+psql (16.2.0, server 16.2.0)
 Type "help" for help.
 
 bdrdb=#
@@ -334,7 +334,7 @@ The proxies provide high-availability connections to the cluster of data nodes f
 ```
 psql -h kaboom,kaftan,kaolin -p 6432 bdrdb
 __OUTPUT__
-psql (15.2.0, server 15.2.0)
+psql (16.2.0, server 16.2.0)
 SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off)
 Type "help" for help.
 

product_docs/docs/pgd/5/quickstart/quick_start_linux.mdx

@@ -124,7 +124,7 @@ Run the [`tpaexec configure`](/tpa/latest/tpaexec-configure/) command to generat
 tpaexec configure democluster \
     --architecture PGD-Always-ON \
     --platform bare \
-    --edb-postgres-advanced 15 \
+    --edb-postgres-advanced 16 \
     --redwood \
     --no-git \
     --location-names dc1 \
@@ -136,7 +136,7 @@ You specify the PGD-Always-ON architecture (`--architecture PGD-Always-ON`), whi
 
 For Linux hosts, specify that you're targeting a "bare" platform (`--platform bare`). TPA will determine the Linux version running on each host during deployment. See [the EDB Postgres Distributed compatibility table](https://www.enterprisedb.com/resources/platform-compatibility) for details about the supported operating systems.
 
-Specify that the data nodes will be running [EDB Postgres Advanced Server v15](https://www.enterprisedb.com/docs/epas/latest/) (`--edb-postgres-advanced 15`) with Oracle compatibility (`--redwood`).
+Specify that the data nodes will be running [EDB Postgres Advanced Server v16](https://www.enterprisedb.com/docs/epas/latest/) (`--edb-postgres-advanced 16`) with Oracle compatibility (`--redwood`).
 
 You set the notional location of the nodes to `dc1` using `--location-names`. You then set `--pgd-proxy-routing` to `local` so that proxy routing can route traffic to all nodes within each location.
 
@@ -297,7 +297,7 @@ You can now run the `psql` command to access the `bdrdb` database:
 ```shell
 psql bdrdb
 __OUTPUT__
-psql (15.2.0, server 15.2.0)
+psql (16.2.0, server 16.2.0)
 Type "help" for help.
 
 bdrdb=#
@@ -356,7 +356,7 @@ The proxies provide high-availability connections to the cluster of data nodes f
 ```shell
 psql -h kaboom,kaftan,kaolin -p 6432 bdrdb
 __OUTPUT__
-psql (15.2.0, server 15.2.0)
+psql (16.2.0, server 16.2.0)
 SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off)
 Type "help" for help.
 

product_docs/docs/pgd/5/routing/raft/01_raft_subgroups_and_tpa.mdx

@@ -21,7 +21,7 @@ The barman nodes don't participate in the subgroup and, by extension, the Raft g
 To create this configuration, you run:
 
 ```
-tpaexec configure pgdgroup --architecture PGD-Always-ON --location-names us_east us_west --data-nodes-per-location 3 --epas 15 --no-redwood --enable_proxy_routing local --hostnames-from hostnames.txt 
+tpaexec configure pgdgroup --architecture PGD-Always-ON --location-names us_east us_west --data-nodes-per-location 3 --epas 16 --no-redwood --enable_proxy_routing local --hostnames-from hostnames.txt 
 ```
 
 Where `hostnames.txt` contains: