Re: pg_multixact not getting truncated

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_multixact not getting truncated
Date: 2014-11-19 20:57:54
Message-ID: 546D0452.100@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/12/2014 06:57 PM, Alvaro Herrera wrote:
>> How did template0 even get a MultiXact? That sounds like they're really abusing the template databases. :( (Do keep in mind that MXID 1 is a special value.)
> No, it's normal -- template0 does not have a multixact in any tuple's
> xmax, but datminxid is set to the value that is current when it is
> frozen.
>

So, to follow up on this: it seems to me that we shouldn't be requiring
freezing for databases where allowconn=false. This seems like a TODO to
me, even possibly a backpatchable bug fix.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-11-19 21:03:03 Re: pg_multixact not getting truncated
Previous Message Adam Brightwell 2014-11-19 20:50:48 Re: Additional role attributes && superuser review