On Tue, May 28, 2013 at 9:07 AM, Stephen Frost <sfr...@snowman.net> wrote: > * Jaime Casanova (ja...@2ndquadrant.com) wrote: >> btw, we can also use a next_extend_blocks GUC/reloption as a limit for >> autovacuum so it will allow that empty pages at the end of the table > > I'm really not, at all, excited about adding in GUCs for this. We just > need to realize when the only available space in the relation is at the > end and people are writing to it and avoid truncating pages off the end- > if we don't already have locks that prevent vacuum from doing this > already. I'd want to see where it's actually happening before stressing > over it terribly much.
+1 autovacuum configuration is already much too complex as it is...we should be removing/consolidating options, not adding them. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
