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 1tlf1a-000xk8-Bt for pgsql-hackers@arkaria.postgresql.org; Sat, 22 Feb 2025 02:13:51 +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 1tlf1Z-0034Eq-IK for pgsql-hackers@arkaria.postgresql.org; Sat, 22 Feb 2025 02:13:49 +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 1tlf1Z-0034Eh-6D for pgsql-hackers@lists.postgresql.org; Sat, 22 Feb 2025 02:13:49 +0000 Received: from mail-pj1-x102f.google.com ([2607:f8b0:4864:20::102f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tlf1S-0004YQ-2I for pgsql-hackers@postgresql.org; Sat, 22 Feb 2025 02:13:48 +0000 Received: by mail-pj1-x102f.google.com with SMTP id 98e67ed59e1d1-2fc1c80cdc8so4441250a91.2 for ; Fri, 21 Feb 2025 18:13:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740190421; x=1740795221; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=216qE20x936q/hFjex9uP66P7TzqfogNe5GstxrqC/w=; b=aJ9TH7Vn7YhW0utbuk0rqZE2qan24vkrYORXQFgQaLpCMHsJ73/7gCuoGZ7OFs9/Qe Ep1Av3Gt6FGlBAsPXWuQnb3qF1dRlPX6Vt24QvYjoYPL0JcM3dZWB7ZJnd5e9Yank8BM He9FP561+DcBLZtG0LQ1fIHIM9g2UMnI0ECEW2AWzEA9byYTQTT8isZxGSnCEE/Aoe8j /A/A3rDkLP8F28hGMU43kUBXCVieH7lFasg+zMxzaQjtEMfXsgb1wYT9TeyrcQUBr4Lz ezx5qzn5oWF1UHRM4EOwQVgcJd5TlpgvyUrH8fZ0NljDIsnB51tRWdin1ILWQwpeAMLn lkmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740190421; x=1740795221; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=216qE20x936q/hFjex9uP66P7TzqfogNe5GstxrqC/w=; b=Mkwo82FCSsOaDXtIGu2VfpTtaCbmvQwK1xAdlPYnwj4Hcilp9x24gAwunfoyKFZsku Sl4ENEGr0HKLq1gTh9UUkkPa4bgUnlPlCU0NVcOqDwAScxjBFLw7RfyU33EBbQ922xN7 +Ao7aH4p11yY7wYxq8w4BaR9LW4qhfULRynjydnUMGfRaOympW7OtH1cvL9/lsKzXSDm vXtMLdMVmZQFPPEhvRdlmJbsYfELOcDbQ31s9hZgXplB/g4UbONPD4dTM/wE4mcCyr0y Uaw2fnPkgnI3zhZs3Pidrwapubn170yY0T2Ss0uQ2UZ4iyhTMZoGRYTcNEFwWi+RzDEM z3Ng== X-Forwarded-Encrypted: i=1; AJvYcCU93aKIE0WDFdnQys5thZnPOneT6srYC0pFaINwU/Kldoow//g88WHiTyc+qufy0uH8tZKLwDCv3U+UPdDm@postgresql.org X-Gm-Message-State: AOJu0YzI2M1hHOqbcEZx0SrmmCQGHDYvUuTpbPbd2Ypr3s3LwI8KOfVS tEBhTqbqVz71xh7CrdxDwibGkKL6OPnFA/jVcaxQ7Ow+speV9BpR1/tzVhCz3nlhmqmfaoOnP0E 4Q7MnU/ohvCd4woiYIAYMDG03HSU= X-Gm-Gg: ASbGnctD8jHHCe4Y1gMBaUpjJBRh2AWFcucwAz1mwDUZM96uo1oB2aSf9HeylLYuIeo aFmTe0EPEgkT2zzPqb6WXJR8ISfT+EGD7ABObG1Q9EGrkqrrfrrCzvIAGyy/Sn1rNGr1/M8sPsw dLDxI1nyUr X-Google-Smtp-Source: AGHT+IFqYseBtBrWqRUIDLZzqhJOnCqLMp8XD+BV9SoKODgomVwyXtqhdrR/aE0by8B5BVCQLh1TCCbpVeirMqfVWuI= X-Received: by 2002:a17:90b:384d:b0:2ee:e18b:c1fa with SMTP id 98e67ed59e1d1-2fce7af3f4cmr8954488a91.28.1740190420962; Fri, 21 Feb 2025 18:13:40 -0800 (PST) MIME-Version: 1.0 References: <54c35fb9-da3a-4754-ab8c-46ed0b612465@vondra.me> <684c70d7-180e-461d-9377-600c2db581ba@vondra.me> <2990641.1740117879@sss.pgh.pa.us> <3132441.1740153303@sss.pgh.pa.us> In-Reply-To: <3132441.1740153303@sss.pgh.pa.us> From: Amit Langote Date: Sat, 22 Feb 2025 11:13:24 +0900 X-Gm-Features: AWEUYZnzDUlLw7KBvL9VlZ-LXzAkgrH2wVOO9cVZnMTsZAP2x-xZCKR-_L9UO70 Message-ID: Subject: Re: generic plans and "initial" pruning To: Tom Lane Cc: Tomas Vondra , Robert Haas , Alvaro Herrera , Andres Freund , Daniel Gustafsson , David Rowley , PostgreSQL Hackers , Thom Brown Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Feb 22, 2025 at 12:55=E2=80=AFAM Tom Lane wrote= : > Amit Langote writes: > > The short of it is that the cached-plan-inval test in the > > delay_execution suite can never be made to work under > > CLOBBER_CACHE_ALWAYS. The test assumes that locks on partitions for a > > reused generic plan are not taken until InitPlan(). However, under > > CLOBBER_CACHE_ALWAYS, generic plans are never reused, so the test's > > assumption never holds. > > Ugh. > > > I see two possible ways to address this: > > > 1. Find a way to disable the cached-plan-inval test in > > CLOBBER_CACHE_ALWAYS builds. However, I haven't found any other test > > that does this. > > > 2. Remove the test altogether, though that might be too drastic. > > Well, you could force matters with "set debug_discard_caches =3D 0" > within the test, but I think that's just a band-aid that would > not make the test fully stable. The point of CLOBBER_CACHE_ALWAYS > is to model random arrival of cache flush events, which is *always* > a possibility due to background activity (autovacuum for instance). > > We do have a couple of other regression tests that rely on > "set debug_discard_caches =3D 0", and I've not seen many buildfarm > failures tracing to that, but I don't trust it a whole lot. > > How badly do you want to keep this test case? It seems fairly > rickety to me, even without this particular concern. Hmm, yeah, I have to admit that even if we address this specific issue, the risk of this test failing again outweighs the likelihood of it catching a real breakage in the deferred lock mechanism. I'll remove the test for now. --=20 Thanks, Amit Langote