On 2014-03-03 07:52:23 -0500, Robert Haas wrote: > And I think that's a pretty worthwhile thing to do, because we get > periodic reports from people who have run VACUUM FULL on a database in > danger of wraparound and then wondered why it did not fix the problem. > The previously-mentioned commit did most of the heavy lifting as far > as tidying that up, but without this adjustment it won't quite get us > over the hump. > > But all that having been said, a deadline is a deadline, so if anyone > wishes to declare this untimely please speak up.
Now, I am obviously not impartial here, but I think it doesn't make sense to whack this code around in two releases if not necessary. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
