O banco não está sendo utilizado e só tem minha conexão nele. Por desencargo de consciência fui rodar o vacuum full de novo e notei que agora funcionou.
De manhã fiz o vacuum full INFO: vacuuming "public.jbpm_variableinstance" INFO: "jbpm_variableinstance": found 0 removable, 12691251 nonremovable row versions in 225883 pages DETAIL: *178441 dead row versions cannot be removed yet.* CPU 5.47s/10.12u sec elapsed 16.81 sec. INFO: analyzing "public.jbpm_variableinstance" INFO: "jbpm_variableinstance": scanned 225883 of 225883 pages, containing 12512810 live rows and *178441 dead rows;* 300000 rows in sample, 12512810 estimated total rows Query returned successfully with no result in 445379 ms. Agora fiz de novo INFO: vacuuming "public.jbpm_variableinstance" INFO: "jbpm_variableinstance": found 178441 removable, 12512810 nonremovable row versions in 225883 pages DETAIL: *0 dead row versions cannot be removed yet*. CPU 7.09s/11.22u sec elapsed 23.57 sec. INFO: "jbpm_variableinstance": scanned 222962 of 222962 pages, containing 12512810 live rows and *0 dead rows;* 300000 rows in sample, 12512810 estimated total rows Query returned successfully with no result in 465956 ms. Será que o autovacuum (ou algum outro processo interno do postgres) poderia estar "lockando" essas linhas que não puderam ser removidas no vacuum? Acho que essa seria a explicação mais lógica, mas é achismo......
_______________________________________________ pgbr-geral mailing list pgbr-geral@listas.postgresql.org.br https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
