Merge pull request #4483 from EnterpriseDB/sf-patroni-bin-name

Add Patroni bin_name setting

advocacy_docs/supported-open-source/patroni/debian11_quick_start.mdx

@@ -27,6 +27,7 @@ export PGUSER=enterprisedb
 export PGGROUP=enterprisedb
 export PGDATA="/var/lib/edb-as/15/main"
 export PGBIN="/usr/lib/edb-as/15/bin"
+export PGBINNAME="edb-postgres"
 export PGSOCKET="/var/run/edb-as"
 ```
 
@@ -38,6 +39,7 @@ export PGUSER=postgres
 export PGGROUP=postgres
 export PGDATA="/var/lib/edb-pge/15/data"
 export PGBIN="/usr/lib/edb-pge/15/bin"
+export PGBINNAME="postgres"
 export PGSOCKET="/var/run/edb-pge"
 ```
 
@@ -134,6 +136,8 @@ postgresql:
   connect_address: "$MY_IP:$PGPORT"
   data_dir: $PGDATA
   bin_dir: $PGBIN
+  bin_name:
+    postgres: $PGBINNAME
   pgpass: /tmp/pgpass0
   authentication:
     replication:
@@ -167,7 +171,7 @@ EOF
 
 `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes.
 
-Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. Create a symbolic link to let Patroni find that binary:
+Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. The `postgresql.bin_name` setting does not exist in Patroni prior to the [`3.0.3` release](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303) and will be silently ignored by older versions. For these versions, create an appropriately named symbolic link that points to the relevant binary:
 
 ```bash
 sudo ln -s /usr/lib/edb-as/15/bin/edb-postgres /usr/lib/edb-as/15/bin/postgres

advocacy_docs/supported-open-source/patroni/rhel8_quick_start.mdx

@@ -27,6 +27,7 @@ export PGUSER=enterprisedb
 export PGGROUP=enterprisedb
 export PGDATA="/var/lib/edb/as15/data"
 export PGBIN="/usr/edb/as15/bin"
+export PGBINNAME="edb-postgres"
 export PGSOCKET="/var/run/edb/as15"
 ```
 
@@ -38,6 +39,7 @@ export PGUSER=postgres
 export PGGROUP=postgres
 export PGDATA="/var/lib/edb-pge/15/data"
 export PGBIN="/usr/edb/pge15/bin"
+export PGBINNAME="postgres"
 export PGSOCKET="/var/run/edb-pge"
 ```
 
@@ -136,6 +138,8 @@ postgresql:
   connect_address: "$MY_IP:$PGPORT"
   data_dir: $PGDATA
   bin_dir: $PGBIN
+  bin_name:
+    postgres: $PGBINNAME
   pgpass: /tmp/pgpass0
   authentication:
     replication:
@@ -169,7 +173,7 @@ EOF
 
 `$MY_IP` and `$MY_NAME` are specific to the local host. Otherwise, the `patroni.yml` configuration is the same on all Patroni nodes.
 
-Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. Create a symbolic link to let Patroni find that binary:
+Patroni expects to find the `postgres` binary in the `bin_dir` location, while the EDB Postgres Advanced Server binary is called `edb-postgres`. The `postgresql.bin_name` setting does not exist in Patroni prior to the [`3.0.3` release](https://github.com/zalando/patroni/blob/master/docs/releases.rst#version-303) and will be silently ignored by older versions. For these versions, create an appropriately named symbolic link that points to the relevant binary:
 
 ```bash
 sudo ln -s /usr/edb/as15/bin/edb-postgres /usr/edb/as15/bin/postgres