Re: Multixacts wraparound monitoring

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: "Pavlov, Vladimir" <Vladimir(dot)Pavlov(at)tns-global(dot)ru>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Multixacts wraparound monitoring
Date: 2016-03-31 20:55:34
Message-ID: CAEepm=2hVSb30+K3Z=YhUdtA90P17jhzy3fGfV+Mx-uLmBwS6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Apr 1, 2016 at 4:31 AM, Pavlov, Vladimir
<Vladimir(dot)Pavlov(at)tns-global(dot)ru> wrote:
> I understand correctly, that number of members cannot be more than 2^32 (also uses a 32-bit counter)?

Correct.

> I had 69640 files in main/pg_multixact/members/, 69640*32*2045 = 4557241600 members, this is normal?

Where did you get 2045 from? I thought it was like this:

number of members = number of member segment files * 1636 * 32
number of multixacts = number of offsets segment files * 2048 * 32

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Reshetov 2016-03-31 21:16:58 Re: Missed LIMIT clause pushdown in FDW API
Previous Message Matthew Syphus 2016-03-31 16:46:56 Re: Create trigger on Materialized View?