Jobin Augustine

This has been addressed in https://github.com/jobinau/pg_gather/commit/61aa456bebaa29f2742aa51f1e4c38dc46d9ce99

This is found to be a major limitation of Aurora which doesn't support PostgreSQL built-in functions like `pg_current_wal_lsn()`. Even though Aurora is claimed to be PostgreSQL compatible. Understanding the WAL...

A Temporary workaround is to replace `CASE WHEN pg_is_in_recovery() THEN pg_last_wal_receive_lsn() ELSE pg_current_wal_lsn() END` with `NULL` in `gather.sql`

One possiblity that I could think about is some users accidently runs the `gather.sql` with `-x` (expanded formatting), instead of `-X` (--no-psqlrc). I such cases the output file might contain...

Commit https://github.com/jobinau/pg_gather/commit/e1114729f40ffc1648c7faed8b84cc17bc209fbc is expected to address this problem also. because there is not separate pg_sleep statement send to server

The possible solution is to limit the list of tables and indexes to 10k. Additional information can be made available though custom analysis queries on the backend data

This is addressed using 2 commits https://github.com/jobinau/pg_gather/commit/be78eef98bf83ddeaa24903910fc2c11799fe91e and https://github.com/jobinau/pg_gather/commit/ba2b6e182cbc931e034174868ac169e7c1741d64

These problems are mainly reported when data is collected from jump/bastion hosts. These errors indicate that the `psql` version is very old. you may check ``` psql --version ``` pg_gather...

This is no a bug. So this will be never fixed

Thank you, @ylacancellera, for reporting this. Yes, this is really a "Future Bug." I think it might be a good idea to wait for the release. What do you think?