AWS RDS PostgreSQL - pg_ls_dir and pg_current_logfile about pgmetrics HOT 3 CLOSED

It appears the AWS RDS superuser does not have permissions to pg_ls_dir and pg_current_logfile

Yes, this is a known issue. It does not hinder the working of pgmetrics however. The only side effect is log pollution.

One change would be to use pg_ls_waldir (v10+) and pg_ls_archive_statusdir (v12+) instead. The other option is to include a flag to skip this step. Or perhaps somehow determine that pgmetrics is connected to AWS RDS and not attempt to call pg_ls_dir/pg_current_logfile if so.

Also, is there any plans to modify this to work on opensource PostgreSQL and AWS RDS PostgreSQL?

It works with both already. Do you see any errors when you use it?

from pgmetrics.

No, I see no errors. The impact is the "log pollution" as we send our logs to other tools to parse and do analytics. Having cleaner logs would be best so we do not have to write code to clean out the "log pollution".

from pgmetrics.

Fixed by 09811f3, e05e2b9, 4d74213 and 0ab5237. Will be available in next release (v1.9.0), or you can try it directly by compiling from master (run go get github.com/rapidloop/pgmetrics/cmd/pgmetrics from an empty directory, builds to ~/go/bin/pgmetrics).

from pgmetrics.