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.96) (envelope-from ) id 1vd3YB-00DS1T-2v for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Jan 2026 09:40:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vd3YA-007FJa-2F for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Jan 2026 09:40:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vd3YA-007FJS-0r for pgsql-hackers@lists.postgresql.org; Tue, 06 Jan 2026 09:40:27 +0000 Received: from forwardcorp1a.mail.yandex.net ([2a02:6b8:c0e:500:1:45:d181:df01]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vd3Y8-004U99-0R for pgsql-hackers@lists.postgresql.org; Tue, 06 Jan 2026 09:40:25 +0000 Received: from mail-nwsmtp-smtp-corp-main-69.vla.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-69.vla.yp-c.yandex.net [IPv6:2a02:6b8:c1f:3a87:0:640:845c:0]) by forwardcorp1a.mail.yandex.net (Yandex) with ESMTPS id 6275FC0154; Tue, 06 Jan 2026 12:40:15 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6bf:8080:63d::1:34]) by mail-nwsmtp-smtp-corp-main-69.vla.yp-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id DelnP23DrqM0-7nIbIUSV; Tue, 06 Jan 2026 12:40:14 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1767692415; bh=ZRyRiHVoKxBHk3gun56w08BEDmME2FV6lbh8+cYmPBM=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=hJuMOfFfcemZBVbBob47PY+yJT0aMVio52rndG/KQeYKNw88tEw1vJ4kq0MtDIv36 QSpxmHTlx4WTa1nqqiuWvyMvC4avEqkbihXYqIts61BljcROe7650B3RjwBZEN8QXW KdSLRxKB/N78HmPmgzeZIfW2V6v2Ae1SnrN0GDfs= Authentication-Results: mail-nwsmtp-smtp-corp-main-69.vla.yp-c.yandex.net; dkim=pass header.i=@yandex-team.ru Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\)) Subject: Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) From: Andrey Borodin In-Reply-To: Date: Tue, 6 Jan 2026 14:40:03 +0500 Cc: Kirill Reshke , Chao Li , Xuneng Zhou , Andres Freund , Robert Haas , PostgreSQL Hackers , Heikki Linnakangas Content-Transfer-Encoding: quoted-printable Message-Id: <4379FDA3-9446-4E2C-9C15-32EFE8D4F31B@yandex-team.ru> References: <2wk7jo4m4qwh5sn33pfgerdjfujebbccsmmlownybddbh6nawl@mdyyqpqzxjek> <6BC5DBAB-6084-4BB8-8450-52E9648AB021@gmail.com> <7F5BCD7A-764D-4D8D-8E27-6F2CAAEA1CEE@gmail.com> To: Melanie Plageman X-Mailer: Apple Mail (2.3826.700.81) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 6 Jan 2026, at 00:24, Melanie Plageman = wrote: >=20 > I've tried to take an attempt to review some patches of this patchset. = It's huge and mostly polished. In a step "Pass down information on table modification to scan node" you = pass SO_HINT_REL_READ_ONLY flag in IndexNext() and = BitmapTableScanSetup(), but not in IndexNextWithReorder() and = IndexOnlyNext(). Is there a reason why index scans with ordering cannot = use on-access VM setting? Also, comment about visibilitymap_set() says "Callers that log VM = changes separately should use visibilitymap_set()" as if = visibilitymap_set() is some other function. Best regards, Andrey Borodin.=