On Mon, 2022-11-28 at 04:05 +, senor wrote:
> I'm a little late getting back to this but still have no solution.
>
> I had inadvertently executed a vacuum freeze on a table that pg_stat_activity
> indicated was currently being autovacuumed. The manual vacuum succeeded while
> leaving the previ
I'm a little late getting back to this but still have no solution.
I 100% agree that updating postgres is best. The usual excuses for not updating
apply. It will be done when it is allowed to be done. It remains 11.4 for now.
I read through the changelogs up through 11.18 and didn't see anything
On Fri, 2022-11-04 at 02:50 +, senor wrote:
> I'm still trying to get a better understanding of the autovacuum process.
> This is a different postgres installation as my previous posts and confusing
> me in new ways.
> Still 11.4 running on CentOS 7 and 8 nvme in software raid
Not good. Tha
Hi All,
I'm still trying to get a better understanding of the autovacuum process.
This is a different postgres installation as my previous posts and confusing me
in new ways.
Still 11.4 running on CentOS 7 and 8 nvme in software raid
This issue started with postgres "...not accepting commands t
