| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: VACUUM FULL/CLUSTER doesn't update pg_class's pg_class.relfrozenxid |
| Date: | 2014-03-03 13:05:37 |
| Message-ID: | 20140303130537.GA16654@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-03-03 13:32:27 | Re: Securing "make check" (CVE-2014-0067) |
| Previous Message | Robert Haas | 2014-03-03 12:52:23 | Re: VACUUM FULL/CLUSTER doesn't update pg_class's pg_class.relfrozenxid |