> As a superuser, rename pg_stat_reset inside one of the commonly affected databases: > alter function pg_stat_reset rename to hey_stop_running_pg_stat_reset_already; > Then see who starts complaining. Additionally, your server log will get helpful entries like this:
Thanks for the tip Greg - that's very clever! I've done this just now, and will check back tomorrow to see if there's any corresponding error message. NB: I hadn't originally realized that the system functions (ie pg_*) were created for each database, so I had renamed only the one in the postgres database, thinking it was global (ie I'll blame this on my Oracle days ;-)). Now I renamed the function under one database that had been verified as getting its stats reset on a daily basis. Hopefully tomorrow we'll get more interesting info! -Steeve On Sat, Nov 23, 2024 at 11:50 AM Greg Sabino Mullane <htamf...@gmail.com> wrote: > As a superuser, rename pg_stat_reset inside one of the commonly affected > databases: > > alter function pg_stat_reset rename to > hey_stop_running_pg_stat_reset_already; > > Then see who starts complaining. Additionally, your server log will get > helpful entries like this: > > ERROR: function pg_stat_reset() does not exist > > Cheers, > Greg > >
