On Thu, Jan 20, 2011 at 12:04 PM, Kevin Grittner <Kevin.Grittner@xxxxxxxxxxxx> wrote: > "Charles.Hou" <givemeegn@xxxxxxxxx> wrote: > >> my postgresql version is 8.1.3 > > Ouch! That's getting pretty old; I hope it's not on Windows. > > http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy > > http://www.postgresql.org/about/news.865 > >> you means the newer version has a virtual transaction ID. and >> what's the maxmium of this virtual id, also 4 billion ? >> should i also vacuum freeze the virtual id in the new version when >> it reached the 4 billion? > > The point is to reduce maintenance, not increase it -- you don't > need to worry about cleaning these up. And in fact, in more recent releases - particularly 8.4 and 9.0, the need to worry about vacuum in general is much less. There are many improvements to both vacuum generally and autovacuum in particular that make things much better, including enabling autovacuum by default, multiple autovacuum worker threads, the visibility map, and so on. It's fairly likely that everything that the OP is struggling with on 8.1 would Just Work on 8.4 or 9.0. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
