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
[+] add graceful fallback for local log parsing (#1109)
* Check privileges before invoking `ParseLogsLocal()`
I didn't consider testing all possible directory and
file privileges, assuming the default setup so
if a user (postgres or superuser) has read privilege
on the logs directory then he should be able to
read all the files.
* Update log parsing docs
We don't neccesarily require superuser privileges in local
mode, e.g, `postgres` user will be enough as he can access
the log dir and its content.
* Move `... on the same host ...` log message to the first condition
Copy file name to clipboardExpand all lines: docs/reference/advanced_features.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ Only event counts are stored - no error messages, usernames, or other details. E
46
46
47
47
pgwatch automatically selects between two parsing modes:
48
48
49
-
1.**Local mode** - Used when pgwatch runs on the same host as the database server and can access log files directly. Requires superuser privileges and `pg_read_all_settings` role.
49
+
1.**Local mode** - Used when pgwatch runs on the same host as the database server and can access log files directly. Requires OS user with read privileges on the logs directory and its files and `pg_read_all_settings` role.
50
50
51
51
2.**Remote mode** - Used when pgwatch runs on a different host. Requires `pg_monitor` role and execute privilege on `pg_read_file()`.
0 commit comments