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 1sIy6n-001cA3-Gw for pgsql-hackers@arkaria.postgresql.org; Sun, 16 Jun 2024 22:12:21 +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 1sIy6j-00AH7q-SV for pgsql-hackers@arkaria.postgresql.org; Sun, 16 Jun 2024 22:12:18 +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 1sIy6j-00AH7h-9N for pgsql-hackers@lists.postgresql.org; Sun, 16 Jun 2024 22:12:18 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sIy6d-0021gg-2c for pgsql-hackers@postgresql.org; Sun, 16 Jun 2024 22:12:17 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-25931dc75bbso617386fac.3 for ; Sun, 16 Jun 2024 15:12:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1718575928; x=1719180728; darn=postgresql.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:to:from:date:from:to:cc:subject:date:message-id :reply-to; bh=oqh/nAGGbSTJ0aiJ6DJ5w2SkJ81XmAKAQ+sGQ9VhXuw=; b=WJUqVPaZNkEUajCbhdRKkTySb4PxKL2GQdtYkH0K2GCWWy4Ixe8tpK2AdvxKi75iwX qRQ0YGJz022cfhG7B9lAIlPMIgKSJuy8L1G081GBcSxbcsFxxHXXDDXASL/jg/DbQ4Mo UcqRJtFnAKPSp6GK7LxHeRyhBj2PZI8YKDLig= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718575928; x=1719180728; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=oqh/nAGGbSTJ0aiJ6DJ5w2SkJ81XmAKAQ+sGQ9VhXuw=; b=DR0qsMMMuf1dExI/8pGdiJXBQlfWHfAGqSu9ejZQQ9ZpV6ntOVh1Vb9Dh9w8VyxAiS 1ggXM3xkfi3yvMukEy4ksZyRcBVpaLAcspwngDXhLAyW42knDffEnlxj+LIcfNqGrEcm UquhbDQ4aVEvM8xwQZMjYFOGPBbsp1EfNBTx7AsTxzUZp/jgMCBOIKmheXp2BdazUsn7 BxjG9sVUyXkCAntDswMGPxOX2pCu9fakG3Zbz2hxKTrL1W+dTYU7w5FB7EUUOsVUSy/t IkPfqw0iYeebvPflf91dqcsbVaehAet9x5/8/XJulkw9cdfqNEvYjbONOWztUDugHR/s pwwA== X-Gm-Message-State: AOJu0YxDSa1DOfPqrm7Ir3SF14sDOs5st3MDxqiawTOV41jMHvnFuw7s SG1oL2n7vTdOa/CCmkgjXVIakbyilTYpcZJLSvOS3mXJRCkWPv7TtX+qWMb5fe9j20xynqFkkxE = X-Google-Smtp-Source: AGHT+IEcQlgWScc6C26aHbwjJm7LZlLUB4kOtManb6LNwrj7ovELO1gRq8bXXHNPQ6G0Xt2EIFNrmA== X-Received: by 2002:a05:6870:a54d:b0:254:8908:4281 with SMTP id 586e51a60fabf-25842af7d8amr8569902fac.44.1718575928080; Sun, 16 Jun 2024 15:12:08 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id 586e51a60fabf-2567a9a8d95sm2255236fac.16.2024.06.16.15.12.07 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Jun 2024 15:12:07 -0700 (PDT) Date: Sun, 16 Jun 2024 15:12:05 -0700 From: Noah Misch To: pgsql-hackers@postgresql.org Subject: Re: Inval reliability, especially for inplace updates Message-ID: <20240616221205.24.nmisch@google.com> References: <20240523000548.58.nmisch@google.com> <20240615223718.42.nmisch@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240615223718.42.nmisch@google.com> User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Jun 15, 2024 at 03:37:18PM -0700, Noah Misch wrote: > I'm attaching the implementation. I'm withdrawing inplace150-inval-durability-atcommit-v1.patch, having found two major problems so far: 1. It sends transactional invalidation messages before ProcArrayEndTransaction(), so other backends can read stale data. 2. It didn't make the equivalent changes for COMMIT PREPARED.