Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lvZxT-00075f-LV for pgsql-docs@arkaria.postgresql.org; Tue, 22 Jun 2021 06:32:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lvZxQ-0007sg-Pj for pgsql-docs@arkaria.postgresql.org; Tue, 22 Jun 2021 06:32:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lvZxQ-0007qf-Ee for pgsql-docs@lists.postgresql.org; Tue, 22 Jun 2021 06:32:24 +0000 Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lvZxN-00023h-Fn for pgsql-docs@lists.postgresql.org; Tue, 22 Jun 2021 06:32:23 +0000 Received: by mail-wm1-x32c.google.com with SMTP id c84so11942328wme.5 for ; Mon, 21 Jun 2021 23:32:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=Y/PWERs8aJfiAAB0FT04mhW2XVU29JZqlIt9zQisX0g=; b=v3QCpJ/03Yl7ZSP/3ZM4/chbf+R4u/qi8dfi0u/RTnmTt10msJX1FM9+2EfopHsvYX +fPEPjnfrUYnKiyQ+YCOfi8J6NS0UHAy47rcGeAD88IaLBg/F6YjlMvUf0/jAgVYm7+w KdCvQAp/CBpL7f65UsEAFv4N9QDanNjaQovTt1mQUjFC5dYkXTG5Ph9UcuCWM3DGvX44 4PsS88CNO/MH7oPLUINHj4NVC2Tg1Bt8gyenfYah5mby7C7oUBEO0gJsenQJnFZaQ5xG aC0hySRjGuJIG4CRHtLDRXq+Ez7hr3mdE4DAfH7myxvAhwQy5t32rwng2NcTB+aJFNMH b3RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=Y/PWERs8aJfiAAB0FT04mhW2XVU29JZqlIt9zQisX0g=; b=WWINU4h/4y0VTLZjEUsyB+3+Ucq+paD0pRwCrkwNWb22RB1MbSvuPdlLxB4yhZ9m1G K6IvaaCw2PPM4FH4Bij/9W9t2DMV46SPoacRogaaAELl4klfFmhKlAKZq9Zg5coi9Hvu uVyxwwgccYPWr9+xy9NT26TzTKNI8brPSha+acHO9esr3DZuU+zpiVOK7MwjovbzXhir 4ATrCFAOpcTmRy8nYWl00TiLcOzXfoP4eBQSDXZAggaB/Et/0aqpuBKVpdPPa5KA2j9e vUB6ecZ/egbVDQgvm5hAzIh1sDw5I1b3J32GO2hntxgsXiHRvP2gddJoCU5jS7RJSAOH OTkw== X-Gm-Message-State: AOAM533phNE7Fpit0z+szCe0z0rJCKNRDO4ELJmARSF/Ip345OqiGzeS vfmUAc7Oc0xmZt/M9MQgH82M8w== X-Google-Smtp-Source: ABdhPJwdPo35ZQvDphsb0l/3KQ5j1brnvBIb3NUcDP63Hc0DJwku40o9fx06Ij6MY+tQY9VvrwPaNw== X-Received: by 2002:a1c:25c6:: with SMTP id l189mr2706045wml.49.1624343539564; Mon, 21 Jun 2021 23:32:19 -0700 (PDT) Received: from localhost.localdomain (217-149-168-3.nat.highway.telekom.at. [217.149.168.3]) by smtp.gmail.com with ESMTPSA id k13sm6408253wrp.73.2021.06.21.23.32.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Jun 2021 23:32:19 -0700 (PDT) Message-ID: Subject: Re: 24.1.5.1. Multixacts And Wraparound From: Laurenz Albe To: Bruce Momjian Cc: eric.mutta@gmail.com, pgsql-docs@lists.postgresql.org Date: Tue, 22 Jun 2021 08:32:18 +0200 In-Reply-To: <20210622025023.GH22121@momjian.us> References: <162395467510.686.11947486273299446208@wrigleys.postgresql.org> <8b8fed1d71a692d9cd72116e42ddde776a12be7e.camel@cybertec.at> <20210622025023.GH22121@momjian.us> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2021-06-21 at 22:50 -0400, Bruce Momjian wrote: > On Fri, Jun 18, 2021 at 08:51:00AM +0200, Laurenz Albe wrote: > > On Thu, 2021-06-17 at 18:31 +0000, PG Doc comments form wrote: > > > In section "24.1.5.1. Multixacts And Wraparound" of > > > https://www.postgresql.org/docs/current/routine-vacuuming.html we find the > > > following sentence towards the end of the section: > > > > > > "...If the amount of used member storage space exceeds the amount 50% of the > > > addressable storage space." > > > > > > I am having trouble parsing "...exceeds the amount 50% of the > > > addressable..." part. > > > > I think that the second "the amount" in the sentence should be removed. > > I think it is worse than that. Here is the full paragraph: > > As a safety device, an aggressive vacuum scan will occur for any table > whose multixact-age is greater than > . Aggressive > vacuum scans will also occur progressively for all tables, starting with > those that have the oldest multixact-age, if the amount of used member > storage space exceeds the amount 50% of the addressable storage space. > Both of these kinds of aggressive scans will occur even if autovacuum is > nominally disabled. > > What does "the amount of used member storage space exceeds 50% of the > addressable storage space" mean? You are right. See MultiXactMemberFreezeThreshold for the whole story. What about: As a safety device, an aggressive vacuum scan will occur for any table whose multixact-age (see ) is greater than . Also, if the storage occupied by multixacts exceeds 2GB, aggressive vacuum scans will occur more often for all tables, starting with those that have the oldest multixact-age. Both of these kinds ... I hope I read the source right concerning the 2GB. Yours, Laurenz Albe