You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,7 @@ to activate the automatic binding. This again might not be suitable for all use
85
85
86
86
### nonlocal bind
87
87
88
-
If you can't set `listen_addresses` to a wildcard address, you can explicitly specify only those adresses that you want to listen to.
88
+
If you can't set `listen_addresses` to a wildcard address, you can explicitly specify only those addresses that you want to listen to.
89
89
However, if you add the virtual IP to those addresses, PostgreSQL will fail to start when that address is not yet registered on one of the interfaces of the machine.
90
90
You need to configure the kernel to allow "nonlocal bind" of IP (v4) addresses:
91
91
@@ -123,9 +123,9 @@ When using different configuration sources simultaneously, this is the precedenc
123
123
124
124
All flags and file entries are written in lower case. To make longer multi-word flags and entries readable, they are separated by dashes, e.g. `retry-num`.
125
125
126
-
If you put a flag or file entry into uppercase and replace dashes with underscores, you end up with the format of environment variables. To avoid overlapping configuration with other applications, the env variables are additionall prefixed with `VIP_`, e.g. `VIP_RETRY_NUM`.
126
+
If you put a flag or file entry into uppercase and replace dashes with underscores, you end up with the format of environment variables. To avoid overlapping configuration with other applications, the env variables are additional prefixed with `VIP_`, e.g. `VIP_RETRY_NUM`.
127
127
128
-
This is a list of all avaiable configuration items:
128
+
This is a list of all available configuration items:
@@ -144,7 +144,7 @@ This is a list of all avaiable configuration items:
144
144
|`retry-after`|`VIP_RETRY_AFTER`| no |`250`| The time to wait before retrying interactions with components outside of vip-manager. Measured in ms. Defaults to `250`. |
145
145
|`retry-num`|`VIP_RETRY_NUM`| no |`3`| The number of times interactions with components outside of vip-manager are retried. Defaults to `3`. |
146
146
|`etcd-ca-file`|`VIP_ETCD_CA_FILE`| no |`/etc/etcd/ca.cert.pem`| A certificate authority file that can be used to verify the certificate provided by etcd endpoints. Make sure to change `dcs-endpoints` to reflect that `https` is used. |
147
-
| `etcd-cert-file|`VIP_ETCD_CERT_FILE`| no |`/etc/etcd/client.cert.pem`| A client certificate that is used to authenticate against etcd endpoints. Requires `etcd-ca-file` to be set as well. |
147
+
|`etcd-cert-file`|`VIP_ETCD_CERT_FILE`| no |`/etc/etcd/client.cert.pem`| A client certificate that is used to authenticate against etcd endpoints. Requires `etcd-ca-file` to be set as well. |
148
148
|`etcd-key-file`|`VIP_ETCD_KEY_FILE`| no |`/etc/etcd/client.key.pem`| A private key for the client certificate, used to decrypt messages sent by etcd endpoints. Required when `etcd-cert-file` is specified. |
149
149
|`verbose`|`VIP_VERBOSE`| no |`true`| Enable more verbose logging. Currently only the manager-type=hetzner provides additional logs. |
0 commit comments