Reverting to old Prom caching behaviour

[kmoppel]

Hey pgwatchers!

Just saw that postgres-ai's version of pgwatch these days is a very thin wrapper around the baseline - patching 2 things (plus custom config and dashboards), one of them being my main annoyances with pgwatch as well - the Prom "non-caching" feature. So maybe it's time to finally fix it?

It's a very unique Prom behaviour currently in my opinion and makes ad-hoc testing / troubleshooting really annoying and causing gaps in prod data as well.

Wdyt @pashagolub @0xgouda ? I could do a PR...I think we had some discussion on it in the past already as well but can't find it currently

Introduced here: https://github.com/cybertec-postgresql/pgwatch/pull/790/changes
Postgres.ai workaround here: https://github.com/postgres-ai/postgresai/blob/main/pgwatch/Dockerfile#L66

[pashagolub]

Hey Kaarel! Fixed already! Goes to the very next major release #1289

Feel free to test! :)

[kmoppel]

Wow, that was fast 😅 Did a quick check and seems to work as well, so very nice, thanks!