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 1vo4qX-00FFPw-14 for pgsql-general@arkaria.postgresql.org; Thu, 05 Feb 2026 19:16:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vo4qV-000bJy-17 for pgsql-general@arkaria.postgresql.org; Thu, 05 Feb 2026 19:16:55 +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 1vo4qU-000bJq-22 for pgsql-general@lists.postgresql.org; Thu, 05 Feb 2026 19:16:54 +0000 Received: from fhigh-b5-smtp.messagingengine.com ([202.12.124.156]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vo4qS-00000000jD2-1BqC for pgsql-general@lists.postgresql.org; Thu, 05 Feb 2026 19:16:53 +0000 Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfhigh.stl.internal (Postfix) with ESMTP id A67BA7A004D; Thu, 5 Feb 2026 14:16:50 -0500 (EST) Received: from phl-imap-13 ([10.202.2.103]) by phl-compute-06.internal (MEProxy); Thu, 05 Feb 2026 14:16:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sophiebits.com; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1770319010; x=1770405410; bh=x4Tcnxc5jE1uzDHpYajpzMAPvYqNzzD3fPJ5Ns0y3dw=; b= nEfOYYf0l42bB5RAGaA/1efl1qH/Kcz6ZGhmWAP7xe7e+6FpLIV2x9Ld4ieSGLV9 8U+weKLEoSKjE/PP05oN5TGHycAZf57lW2UV302rXn9M5e8OpsOygVsqnTi/1xgY UVwFa9BlBbX9ilpOczfj8r12OsO5BZ2ugssYD30jXVyZWkz+oGIS2RqR4qsP3fyc a4ZpFSmFSYS75wQB2HYuzisXdzPuJKOvn1mCLxqmMmPmWLRBJwXP0+9DhJfEJ28o vbft2OB1eY/iZ2MPRgnR0v/qgQL6mU9sttSPddpFqJP8RhsCM0VpQKoN5x64GH30 6G7FakpNq2KNHO1JXWi18g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1770319010; x=1770405410; bh=x 4Tcnxc5jE1uzDHpYajpzMAPvYqNzzD3fPJ5Ns0y3dw=; b=fHgCrWR0h64jnMtfv 2g2QvUhWKfk31mVTcnONc5s3Etcy1Axy4etCxrRZQ9vfNdmx5CPaUesxfq1cLExM Z3/6o4f8qsttdIdAbD55i0HgdrRviMZaRnrffJ/MkP+E+A0oJJFygVQMFOaCCJoA fkS5SNeMC0oEfwFciGBJ7FXdY2UtOMVHVTaYD3OFsVhFjJ2xPDTVr14RfMoHQd7U Bb2hoO887BL5U+Vu2xikcx2hGQn5ZKV2XH7SZ+NMMP+6Swspb2vLgPUs7njA0p7E tIPM+YIpzA36Zy9LMoBKdil1jijope8aGnLrOvLvh/MWu5iLCyMSFGcEbGMNMo81 /YkOw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgddukeeiudduucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepofggfffhvffkjghfufgtgfesthejredtredttdenucfhrhhomhepfdfuohhphhhi vgcutehlphgvrhhtfdcuoehpghesshhophhhihgvsghithhsrdgtohhmqeenucggtffrrg htthgvrhhnpeektddtfedutefgleehtdektdekffdvieekleejffdtteehieejteegfeet jeefjeenucffohhmrghinhepshhtrggtkhhovhgvrhhflhhofidrtghomhenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpghesshhophhhihgv sghithhsrdgtohhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprh gtphhtthhopegsvghrnhhitggvrdhsohhuthhhvgihsehgmhgrihhlrdgtohhmpdhrtghp thhtohepphhgshhqlhdqghgvnhgvrhgrlheslhhishhtshdrphhoshhtghhrvghsqhhlrd horhhg X-ME-Proxy: Feedback-ID: i64f94250:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 29CD333E0099; Thu, 5 Feb 2026 14:16:50 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface MIME-Version: 1.0 X-ThreadId: AztObckWXd0V Date: Thu, 05 Feb 2026 11:16:29 -0800 From: "Sophie Alpert" To: "Bernice Southey" , pgsql-general@lists.postgresql.org Message-Id: <702bca7b-711f-4d7c-ad39-dead6a628374@app.fastmail.com> In-Reply-To: References: Subject: Re: Is this expected concurrency behaviour for EvalPlanQual and ctid? Content-Type: text/plain Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bernice, Perhaps you'll find this explanation I wrote around interactions between EvalPlanQual and ctid filters helpful: https://stackoverflow.com/a/79757326/49485 The short answer is that even after my fix, you likely don't want to filter an UPDATE or DELETE on ctid values that were first retrieved in the same SQL statement, because the ctid can have changed in between the time of the initial read and the time of locking (and thus the recheck will fail). Sophie