Re: pg_multixact not getting truncated

From: Greg Stark <stark(at)mit(dot)edu>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_multixact not getting truncated
Date: 2014-11-21 18:01:35
Message-ID: CAM-w4HNL6GGpt8NtkKEpo+VWLVM4VyJHXxF4Z=CHyECXR8NjPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 20, 2014 at 9:21 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Well, the first thing that comes to mind is that template0 should be
> "permanently frozen". That is, all objects in it should be created with
> frozen xid and mxids. After all, nobody can modify anything in it.

This is actually the way it used to be. It was changed because it was
discovered there was some case where an unfrozen xid would end up in
template0 anyways and for some reason it was hard to be sure to avoid it. I
don't recall exactly what the situation was that triggered it but the
argument was made then that it was safest to just include template0 in
autovacuum rather than depend on getting this 100% right and risk
corruption.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-11-21 18:05:47 Re: psql \sf doesn't show it's SQL when ECHO_HIDDEN is on
Previous Message Josh Berkus 2014-11-21 17:55:01 Re: Turning recovery.conf into GUCs