Re: Rework the way multixact truncations work

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Rework the way multixact truncations work
Date: 2015-10-27 20:51:45
Message-ID: 562FE3E1.5070303@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/27/2015 07:44 AM, Andres Freund wrote:
>> Unlinking old pg_clog files is strictly an optimization. If you were to
>> > comment out every unlink() call in slru.c, the only ill effect on CLOG is the
>> > waste of disk space. Is the same true of MultiXact?
> Well, multixacts are a lot larger than the other SLRUs, I think that
> makes some sort of difference.

And by "a lot larger" we're talking like 50X to 100X. I regularly see
pg_multixact directories larger than 1GB.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-10-27 20:52:41 quieting DEBUG3
Previous Message Gurjeet Singh 2015-10-27 19:48:36 Re: Limit GIST_MAX_SPLIT_PAGES to XLR_MAX_BLOCK_ID