Hi, On 2017-08-09 16:30:03 -0400, Alvaro Herrera wrote: > > One particular table before vacuum full: > > > > relname | relminmxid | table_size > > ------------------------------+------------+------------ > > delayed_jobs | 1554151198 | 21 GB > > > > And after vacuum full: > > > > relname | relminmxid | table_size > > --------------+------------+------------ > > delayed_jobs | 1554155465 | 6899 MB > > > > Shouldn't be the relminmxid changed after vacuum full, or am I not > > understanding something? FWIW, VACUUM FULL isn't a good tool to use here. It's commonly way more expensive than a normal vacuum (it rewrites the entire table, and rebuilds indexes). > But it did change ... the problem is that it didn't change enough (only > 4000 multixacts). Maybe your multixact freeze min age is too high? > Getting rid of 15 GB of bloat is a good side effect, though, I'm sure. I wonder if there's longrunning transactions preventing cleanup. I suggest checking pg_stat_activity, pg_prepared_xacts, pg_replication_slot for older stuff. Greetings, Andres Freund -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
