I do see older backend_start values (from around 6 hours ago). However I am confused as to how a connection to one database in a cluster can prevenr vacuum from cleaning up row versions in a table within another database. How is that possible since onle one database has access to this table?
On Thu, Jun 20, 2019, at 2:37 PM, Rui DeSousa wrote:
In addition to what others have already stated to check; also check for replication slots.select * from pg_replication_slots;
