Andres Freund <and...@2ndquadrant.com> wrote: > I can't imagine that anybody with a large database ran pg > successfully with a small freeze_min_age due to this.
I can't speak to this from personal experience, because at Wisconsin Courts we found ourselves best served by running a database VACUUM FREEZE ANALYZE each night during off-peak hours. > It seems to be broken since the initial introduction of > freeze_table_age in 6587818542e79012276dcfedb2f97e3522ee5e9b. > Trivial patch attached. I didn't see a patch attached. -Kevin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
