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 1wTvzX-000qBA-28 for pgsql-bugs@arkaria.postgresql.org; Mon, 01 Jun 2026 06:19:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wTvzW-009AtN-0o for pgsql-bugs@arkaria.postgresql.org; Mon, 01 Jun 2026 06:19:14 +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.96) (envelope-from ) id 1wTvzV-009AtF-2o for pgsql-bugs@lists.postgresql.org; Mon, 01 Jun 2026 06:19:14 +0000 Received: from forwardcorp1d.mail.yandex.net ([2a02:6b8:c41:1300:1:45:d181:df01]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wTvzU-00000000biA-0RcQ for pgsql-bugs@lists.postgresql.org; Mon, 01 Jun 2026 06:19:13 +0000 Received: from mail-nwsmtp-smtp-corp-main-66.iva.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-66.iva.yp-c.yandex.net [IPv6:2a02:6b8:c0c:bf1f:0:640:c739:0]) by forwardcorp1d.mail.yandex.net (Yandex) with ESMTPS id A8F16807AE; Mon, 01 Jun 2026 09:19:09 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6bf:8080:634::1:1d]) by mail-nwsmtp-smtp-corp-main-66.iva.yp-c.yandex.net (smtpcorp) with ESMTPSA id 8JXjlr1aT4Y0-IGhBCkj0; Mon, 01 Jun 2026 09:19:09 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1780294749; bh=qC38YK6ioEVm7jikkFbq0z4FFaJhGgDez2/Qdr22LWw=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=Y9wyfXgPBg2x/eaESSDlF20KUp6XA8NRYfxTcpGeZtULic8H3ZPfkBemhHGv0YHhE oM7RDLricKHC99bgU2lEMNn2jxhSDXNJgdzCua3U3rLzuvdYvbJo+K0xnyC2r4uotn oJymxsPFEdMslO2XNdE4gqFLX3NFTwIcqZiPIipU= Authentication-Results: mail-nwsmtp-smtp-corp-main-66.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.600.51.1.1\)) Subject: Re: Possible G2-item at SERIALIZABLE From: Andrey Borodin In-Reply-To: Date: Mon, 1 Jun 2026 11:18:58 +0500 Cc: PostgreSQL mailing lists Content-Transfer-Encoding: quoted-printable Message-Id: <802C6ECE-8D49-4E1A-83CB-A45C8E4EBFAD@yandex-team.ru> References: <165342c0-0c75-461e-b334-b997639ad48d@aphyr.com> <84AC98E5-3387-40A5-A258-C6E354349154@yandex-team.ru> To: Kyle Kingsbury X-Mailer: Apple Mail (2.3864.600.51.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 1 Jun 2026, at 06:49, Kyle Kingsbury wrote: >=20 > This behavior disappears Glad that was it. There's a separate case I'd still like your eyes on: = savepoints. README-SSI says predicate locks must survive a subtransaction rollback, = because the subxact's reads still affect what the top transaction writes. By that = same reasoning, shouldn't a serialization failure raised while checking such a read DooM = the top transaction, rather than being swallowed by ROLLBACK TO SAVEPOINT? Best regards, Andrey Borodin.=