@@ -9,7 +9,7 @@ at the upper right corner):
9
9
To treat the data correctly, you need deep Postgres knowledge. Each report
10
10
consists of 3 sections: Observations, Conclusions, and Recommendations.
11
11
Observations are filled automatically. As for Conclusions and Recommendations
12
- sections, as of October 2019, only limited number of reports are auto-generated.*
12
+ sections, not all reports are auto-generated.*
13
13
14
14
15
15
# About
@@ -153,7 +153,7 @@ cd postgres-checkup
153
153
Let's make a report for a project named ` prod1 ` . Assume that we have two servers,
154
154
` db1.vpn.local ` and ` db2.vpn.local ` .
155
155
156
- Postgres-checkup automatically detects which one is a master:
156
+ Postgres-checkup automatically detects which one is the master:
157
157
158
158
``` bash
159
159
./checkup -h db1.vpn.local -p 5432 --username postgres --dbname postgres --project prod1 -e 1
@@ -168,7 +168,8 @@ project directory, as epoch of check `1`. Epoch is a numerical (**integer**) sig
168
168
For example: in half a year we can switch to "epoch number ` 2 ` ".
169
169
170
170
` -h db2.vpn.local ` means: try to connect to host via SSH and then use remote ` psql ` command to perform checks.
171
- If SSH is not available the local 'psql' will be used (non-psql reports will be skipped).
171
+ If SSH is not available the local 'psql' will be used (non-psql reports will be skipped) to establish
172
+ Postgres connection. If you want to avoid "guessing", use ` -ssh-hostname ` or ` --pg-hostname ` .
172
173
173
174
Also, you can define a specific way to connect: SSH or ` psql ` :
174
175
0 commit comments