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 1stCxh-00EPAs-5y for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Sep 2024 21:20:45 +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 1stCxg-00EmN7-A9 for pgsql-hackers@arkaria.postgresql.org; Tue, 24 Sep 2024 21:20:44 +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 1stCxg-00EmMz-0v for pgsql-hackers@lists.postgresql.org; Tue, 24 Sep 2024 21:20:44 +0000 Received: from mail-pl1-x62b.google.com ([2607:f8b0:4864:20::62b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1stCxb-000u8K-S4 for pgsql-hackers@lists.postgresql.org; Tue, 24 Sep 2024 21:20:43 +0000 Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-2053a0bd0a6so60337405ad.3 for ; Tue, 24 Sep 2024 14:20:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1727212839; x=1727817639; darn=lists.postgresql.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=NHK1vmEZt4YSUNLs8CfFWvx6AMC7si6CPQ4bWY54bLs=; b=QHHaT9zjuc2mr5TtqkMHRoQI5GIDVWD2Dpa2x5p1pJ1SfiNBBAfMOBCHBtpwQP+S3Z QCVa5EPo6VfP8obwj8k1/TnfhyyvsOInrDWxuoSDEnv/n0fEX8W/d+nTqnefkVQx9yB8 8uYRMYjjeG+JhMpjo5GZf4D8J1+IYOARS6saM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727212839; x=1727817639; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=NHK1vmEZt4YSUNLs8CfFWvx6AMC7si6CPQ4bWY54bLs=; b=suCi1QWW5llAcfigjAz4wxE8i9xAJa+PpvkhRB2FeohP9Px4uNnKUfUj9qhR5GInBu jw+wMWEiXy+cidGsOcg5fuohgT7OL3GWoFOalqZMUbNcjX1XI/vzQny7hl1vpj4EtP3T wUf47GEmsTz5C24S2ah9oMxMlOtQ78RKLZx5uwXNDqdnljhIiv1iB/mk/FvfIfxVLZV6 BzMlZ8vX4E3HU1WLHpzpJcRlY0dVWkVwOJpIZdFPDU1Q8XbVuauBBGmbrFHhv1tqx1Ak anAZTpwjKHtcemZQlORjq3Hn0puR1CfTR9INI93w6gws46BBDfjfnCBt656zuKrFmFcE /fnA== X-Forwarded-Encrypted: i=1; AJvYcCX/c8/rXHKaWVoFM7qHT0KGy2sCJqluogjCI5+l0nT+EFFyHDds5D9grc3EFTLdCjBFIyYpHPKFa2oRT8Yx@lists.postgresql.org X-Gm-Message-State: AOJu0YwGrPtB77o+2LfJFU2TXFTU6+qOBW+JYHZ+Qgb8hhcGAW11mzpA oHdvMM57DbrOl4K9i0F7WiiokrBT9XAv/r9FcXwYY0JKr+zUGvSB6lkTygmpVg== X-Google-Smtp-Source: AGHT+IEecB5rSmdpQCgUVXYGSYBAfssyWuxaub0NCtgNpCGYcf3SQIrnkzHT1M+ptuQpnF8l0ka8xw== X-Received: by 2002:a17:90b:3c81:b0:2c5:10a6:e989 with SMTP id 98e67ed59e1d1-2e06aff5d17mr504360a91.35.1727212839432; Tue, 24 Sep 2024 14:20:39 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2e058edf183sm1997079a91.6.2024.09.24.14.20.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Sep 2024 14:20:38 -0700 (PDT) Date: Tue, 24 Sep 2024 14:20:36 -0700 From: Noah Misch To: Tom Lane Cc: Xiaoran Wang , pgsql-hackers@lists.postgresql.org, Andres Freund Subject: Re: Recovering from detoast-related catcache invalidations Message-ID: <20240924212036.0a.nmisch@google.com> References: <329632.1705011663@sss.pgh.pa.us> <754826.1705090452@sss.pgh.pa.us> <793469.1705092433@sss.pgh.pa.us> <20240114201411.d0@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240114201411.d0@rfd.leadboat.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 Sun, Jan 14, 2024 at 12:14:11PM -0800, Noah Misch wrote: > On Fri, Jan 12, 2024 at 03:47:13PM -0500, Tom Lane wrote: > > Oh! After nosing around a bit more I remembered systable_recheck_tuple, > > which is meant for exactly this purpose. So v4 attached. > > systable_recheck_tuple() is blind to heap_inplace_update(), so it's not a > general proxy for invalidation messages. The commit for $SUBJECT (ad98fb1) > doesn't create any new malfunctions, but I expect the systable_recheck_tuple() > part will change again before the heap_inplace_update() story is over > (https://postgr.es/m/flat/CAMp+ueZQz3yDk7qg42hk6-9gxniYbp-=bG2mgqecErqR5gGGOA@mail.gmail.com). Commit f9f47f0 (2024-06-27) addressed inplace updates here.