Re: truncating pg_multixact/members

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: truncating pg_multixact/members
Date: 2014-01-21 17:58:51
Message-ID: CA+TgmoYdAKLMGpgtJ_8zPSHARvHcK+sbSBf7bZ1DTD5LwPj_Zg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 20, 2014 at 1:39 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> * I haven't introduced settings to tweak this per table for
> autovacuum. I don't think those are needed. It's not hard to do,
> however; if people opine against this, I will implement that.

I can't think of any reason to believe that it will be less important
to tune these values on a per-table basis than it is to be able to do
the same with the autovacuum parameters. Indeed, all the discussion
on this thread suggests precisely that we have no real idea how to set
these values yet, so more configurability is good. Even if you reject
that argument, I think it's a bad idea to start making xmax vacuuming
and xmin vacuuming less than parallel; such decisions confuse users.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2014-01-21 18:05:31 Bug? could not remove shared memory segment
Previous Message Tom Lane 2014-01-21 17:56:40 Re: Add %z support to elog/ereport?