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 1vkdSv-000QMY-1i for pgsql-hackers@arkaria.postgresql.org; Tue, 27 Jan 2026 07:26:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vkdSu-00CRYt-1e for pgsql-hackers@arkaria.postgresql.org; Tue, 27 Jan 2026 07:26:20 +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 1vkdSu-00CRYk-0D for pgsql-hackers@lists.postgresql.org; Tue, 27 Jan 2026 07:26:20 +0000 Received: from forwardcorp1d.mail.yandex.net ([178.154.239.200]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vkdSq-002Wfi-0f for pgsql-hackers@postgresql.org; Tue, 27 Jan 2026 07:26:19 +0000 Received: from mail-nwsmtp-smtp-corp-main-80.iva.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-80.iva.yp-c.yandex.net [IPv6:2a02:6b8:c0c:5c05:0:640:ff67:0]) by forwardcorp1d.mail.yandex.net (Yandex) with ESMTPS id 3710B80827; Tue, 27 Jan 2026 10:26:13 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6bf:8080:922::1:f]) by mail-nwsmtp-smtp-corp-main-80.iva.yp-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id CQbIQY4BF8c0-8BkzGs7S; Tue, 27 Jan 2026 10:26:12 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1769498772; bh=gr+/xUk3bD4TPpSMrkGL2jYxtcQVhJF+IUDn1gkX/3A=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=1RUX9avFkdnBfMOEdl4JC8E7IJY1qcsM6/2NZv3XKA5Hf37/r8SVqoV2ojvn83dLF tb56Yp6eQVYJQUFN0D/CR5ruBR8jkYH7Vpg6g7EgNJ0jUeSmkg/E4KwTR9wz6Muu+u YG/EBwAhXvAW+PHIe2nDi9TXyX2VjMhBPyzpuFLA= Authentication-Results: mail-nwsmtp-smtp-corp-main-80.iva.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 \(3864.300.41.1.7\)) Subject: Re: Fix gistkillitems & add regression test to microvacuum From: Andrey Borodin In-Reply-To: Date: Tue, 27 Jan 2026 12:26:01 +0500 Cc: pgsql-hackers Content-Transfer-Encoding: quoted-printable Message-Id: <14B4E29D-7B08-4972-BE9E-491A8A6A77CF@yandex-team.ru> References: <449DFC8A-CF54-493E-9366-AF9C73C782AA@yandex-team.ru> To: Kirill Reshke X-Mailer: Apple Mail (2.3864.300.41.1.7) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 23 Jan 2026, at 16:03, Kirill Reshke = wrote: >=20 > On Tue, 20 Jan 2026 at 15:30, Andrey Borodin = wrote: >>=20 >>=20 >>=20 >>> On 15 Jan 2026, at 22:59, Kirill Reshke = wrote: >>>=20 >>> PFA v2 which leaves the test in-place. >>>=20 >>> Also commit message improvements. >>=20 >> Yeah, killtuples for GiST root page is broken. Your patch is fixing = it. >> I don't think we should backpatch this, the bug is harmless, but for = master the patch LGTM. >=20 > Thank you >=20 >> It would be good to assign so->curBlkno and so->curBlkno together. = But gistScanPage() is the only place with access to the block number. >=20 > Sorry, didnt get this take. Sorry, I meant so->curBlkno and so->numKilled are semantically = correlated. But it's difficult to assign them together and this does not = worth refactoring. >=20 >> +# Test gist, but with fewer rows - that killitems used to be buggy. >>=20 >> Probably, in this comment we can explicitly say that killitems was = buggy, but now is fixed. >>=20 >=20 > Hmm, what would be a good wording here? I've opened an English dictionary and it says "used to" can be used with = a meaning "bug was there but it's not anymore". So the patch is RfC IMO. Best regards, Andrey Borodin.=