Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1skscz-003W4Q-7I for pgsql-general@arkaria.postgresql.org; Sun, 01 Sep 2024 22:00:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1skscx-002qWa-5v for pgsql-general@arkaria.postgresql.org; Sun, 01 Sep 2024 22:00:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1skscw-002qUy-LC for pgsql-general@lists.postgresql.org; Sun, 01 Sep 2024 22:00:55 +0000 Received: from mail-wr1-x433.google.com ([2a00:1450:4864:20::433]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1skscu-000CCJ-Uq for pgsql-general@lists.postgresql.org; Sun, 01 Sep 2024 22:00:54 +0000 Received: by mail-wr1-x433.google.com with SMTP id ffacd0b85a97d-371941bbfb0so2305973f8f.0 for ; Sun, 01 Sep 2024 15:00:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bowt-ie.20230601.gappssmtp.com; s=20230601; t=1725228051; x=1725832851; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=w/7o/Ducn0DhNW80Shte3wb6nZDFvK64rQ7VZwtOjiM=; b=mroiFFBhWLG1b1kjmRiFZgaGvJB6Vyg12REhF10kJhRkx/KUhwcT0/rZN2VmL71mPW LKmLlOvxw02A72Y/HhKAyV+s4LuNDwzToeGoL8Ro/vntIFH8vxIxk4pSZJela2kfvgGP gTU+p1h2bH8CUTseYv+XCaQszsgHFq+gwzegLWJgCnMZSS91yR0WfzLJMG6g96t772nN P3M2OxG6kYJYmkMZaJtTKEoPduCob08FgP+MGWmyqSPu8ilQ1ehc4nc3oAVBaI7g9d5q 2+orp2JI/pWGMWsuEKyrU22DzKRtl5y3QNckuAIRu7jV3DvRFFvCjm7X1mJfdFGEkHcI iuXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725228051; x=1725832851; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=w/7o/Ducn0DhNW80Shte3wb6nZDFvK64rQ7VZwtOjiM=; b=uRGLVSpw9nGc9d9B7k6NZO/gSxDcIv8yN0RXcLvTSC2t68OgKR3q0jZtrb9nEKPpbh XCaiWq6TtzupmPZQy8f5R0nJ/V3ougVJ6BD85wcHaeyqK6bcGqSosxuOTkGrLe3qLnfH tNzH4lHiBHjRKeQ+EuBWweKDKqCwg9YjGWSkebr4qLJBTwkh7LM05/S8ZHMC1Ei4zxDw rZPFTwofROBiKpbhHh+8O0aPaEnBF3txcgE/acKq5GrOUKbddVoo4tTGDXajG3HKEvR1 TgzPk9aJCrHbqInFZJUHqjjGKOHL7hI/L65K8LcRBsrHJmnu9+ntT3oG9WQfmCuVHGed EYaQ== X-Gm-Message-State: AOJu0Yx9SeFFBDf++yRhvYue4JWAV0Q+4Y+PFRjfk9JcXFKiqECAesQh jRYrIL3okJb4JgKzWxbEwa4+iBoe2w4DOwC3wCTOoSXeW6if7XmCjFGOaxZOA6eNjR8sKFCaUHd PYQ9sVL/KCEmbWB12BqPMp6Rdg4H7AgCPKLgD2g== X-Google-Smtp-Source: AGHT+IHMEPHq+C4fPpcBIVjJdHNUUSVcuk6D9lblUHEVrCzeJmEE1cmsVlFRtH/cudJoOvqXQGgbCVoNwDkU1GaTVOE= X-Received: by 2002:a05:6000:4f:b0:374:bb0c:c067 with SMTP id ffacd0b85a97d-374bb0cc2fcmr3971257f8f.40.1725228051135; Sun, 01 Sep 2024 15:00:51 -0700 (PDT) MIME-Version: 1.0 References: <3bda0d10-0d60-42b7-9600-abe23d54bb16@postgrespro.ru> In-Reply-To: <3bda0d10-0d60-42b7-9600-abe23d54bb16@postgrespro.ru> From: Peter Geoghegan Date: Sun, 1 Sep 2024 18:00:25 -0400 Message-ID: Subject: Re: PG17 optimizations to vacuum To: Pavel Luzanov Cc: "pgsql-generallists.postgresql.org" , Melanie Plageman , Heikki Linnakangas Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Sep 1, 2024 at 5:44=E2=80=AFPM Pavel Luzanov wrote: > I see a perfectly working TID-store optimization. > With reduced maintenance_work_mem it used only one 'vacuuming indexes' > phase instead of 21 in v16. > But I also expected to see a reduction in the number of WAL records > and the total size of the WAL. Instead, WAL numbers have significantly > degraded. > > What am I doing wrong? That does seem weird. CC'ing the authors of the relevant VACUUM enhancements. --=20 Peter Geoghegan