Open btostevepritchard opened 7 years ago
Thanks for your report.
The problem is that the gatherers for the directory information are running in separate threads, and the stderr output is disabled after those gatherers start.
The fix is in progress.
When I run pg_view, it is repeatedly outputting the message:
Unable to read free space information for the pg_xlog and data directories for the directory /pgsql/9.5/data: [Errno 13] Permission denied: '/pgsql/9.5/data/pg_xlog/lost+found'
This makes the pg_view display unreadable.
I think the reason that this is happening is because I have /pg_xlog mounted on a separate partition (symlinked from $PGDATA/pg_xlog), and Linux has created a lost+found directory:
drwx------ 2 root root 4096 Mar 15 09:20 lost+found
So my postgres user doesn't have access to this directory.
Could pg_view just skip "lost+found" if it's not readable? (obviously it wouldn't know what space is used by it)
Also, if there is an error, could pg_view just show "????" or similar in the appropriate field, rather than the display being rendered unusable by the repeated outputting of error messages?