On Fri, 2009-12-04 at 09:56 -0800, Jeff Davis wrote: > We could put a VACUUM FULL; and a VACUUM (FULL INPLACE); somewhere, > which will cover a lot of the cases you're talking about. However, that > may be a performance consideration especially for people who develop on > laptops.
Let's check it works before worrying about performance. We can take tests out as well as add them once it becomes obvious its working. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
