Given that this seems to have slipped off the hackers radar (or in too hard basket) I have constructed a horrible solution.
I will stop using autovacuum for this relation , I will use our own system to monitor the relation, and I will reset pgclass.reltuples on this relation after vacuum is done to the correct value. I note that vacuum.c has comments in vac_update_relstat that changes to pg_class are done without a transaction. Are there dangers of my doing an update pg_class set reltuples=60000 where relkind='r' and relname='my_hot_table' ? -- View this message in context: http://postgresql.1045698.n5.nabble.com/Inaccuracy-in-VACUUM-s-tuple-count-estimates-tp5806367p5809273.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
