Re: autovacuum not prioritising for-wraparound tables

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Browne <cbbrowne(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: autovacuum not prioritising for-wraparound tables
Date: 2013-01-25 15:59:56
Message-ID: 20130125155956.GE5584@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut escribió:
> On 1/25/13 10:29 AM, Alvaro Herrera wrote:
> > And I do want to get something back-patchable.
>
> Autovacuum has existed for N years and nobody complained about this
> until just now, so I don't see a strong justification for backpatching.

I disagree about people not complaining. Maybe the complaints have not
been specifically about the wraparound stuff and toast tables, but for
sure there have been complaints about autovacuum not giving more
priority to tables that need work more urgently.

> Or is this a regression from an earlier release?

Nope.

> In general, I think we should backpatch less.

I don't disagree with this general principle, but I certainly don't like
the idea of letting systems run with known flaws just because we're too
scared to patch them. Now I don't object to a plan such as keep it in
master only for a while and backpatch after it has seen some more
testing. But for large sites, this is a real problem and they have to
work around it manually which is frequently inconvenient; keep in mind
9.0 is going to be supported for years yet.

That said, if consensus here is to not backpatch this at all, I will go
with that; but let's have the argument first.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2013-01-25 16:20:49 Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)
Previous Message Bruce Momjian 2013-01-25 15:51:39 Re: COPY FREEZE has no warning