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 1sHThw-00812Q-BH for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jun 2024 19:32:32 +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 1sHThu-005g6N-1k for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jun 2024 19:32:30 +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 1sHTht-005g0u-GH for pgsql-hackers@lists.postgresql.org; Wed, 12 Jun 2024 19:32:30 +0000 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sHThs-001Kl0-33 for pgsql-hackers@postgresql.org; Wed, 12 Jun 2024 19:32:29 +0000 Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3d2299e6650so74717b6e.2 for ; Wed, 12 Jun 2024 12:32:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1718220746; x=1718825546; darn=postgresql.org; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=hZxx1ZQHwp6dt63p6z6YfirTNnX0GnzpYbArCp6nLSs=; b=dx+uGzM3+bReFeMMyu7sOvjidqVFy5ePqYkWRRFPC+oJCC92LcO1YbWAKL+4ANDOGO k/7MrNB2zy9azcMgNNhCcdhHsvhth1hx+o7EIRIeHuRZoGXynLOtNMEfmYbzQSlB5lT0 96+qmcJa8+zmuHAT3f3HrqIgbeEQKwSSUCDIA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718220746; x=1718825546; h=user-agent:in-reply-to:content-transfer-encoding :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=hZxx1ZQHwp6dt63p6z6YfirTNnX0GnzpYbArCp6nLSs=; b=cmXxJZe1CWPcAjdir0/trCVECQV0PTS/ar7mHp5n1FX90JEjpUqMxFihEJP4kb92xF x1ecDfiHSlTFnT16oRrgwIAmpVnLwFKHZ9lSgUy0t6QrwzAWYW8MPWEzExzAiQuCZxjy ih0el622pjCQD87dI78SHzEqUwqZB8Rn/dWJ6tJrTAT6vt11BvMiR6esVoHNiBpA5B9i mgrW9M/EGXOzw/ZWgvpZ6bMD8nTBNURL4S8f6VZ2FI8YI7egrLeg/FHvdUZvGH6uw+5G a6IwfUbTNTrmNldG2QuaEKKJ8PSduoo3AieE6u1L46NMIWiD6LqiIkhX3x5jDflP9UiA 5w7A== X-Forwarded-Encrypted: i=1; AJvYcCVrOWinIh0djV14U/XmpFfOc46dM+pMxBQk7rASGetlOjcAc49TYHKFQvOW6Ez8x40VCjIrwn2bEjVcMudiVx2FgSSjJaaBZUONyhat X-Gm-Message-State: AOJu0YwvRPLtCHWZ35d3euVdp/OQvYnK+k+AACvuBcIpR/7/7UU4hQEX rcDGQcCkQx1FReDDgtj/p7abGATFm5fKxvR395qyjFydLHv9fULmhNwYedj9mw== X-Google-Smtp-Source: AGHT+IFCwhqG4g2oooq+3UJynzT/Fug15WQI5CJnKSSLVCS9h5YWWtS9/IMPTuhLSfsMb1wODrMm5w== X-Received: by 2002:a05:6808:f89:b0:3d2:1da4:af63 with SMTP id 5614622812f47-3d23e0e1ee6mr2977245b6e.45.1718220745908; Wed, 12 Jun 2024 12:32:25 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id 5614622812f47-3d2285169c3sm1185915b6e.56.2024.06.12.12.32.24 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Jun 2024 12:32:25 -0700 (PDT) Date: Wed, 12 Jun 2024 12:32:23 -0700 From: Noah Misch To: Robert Haas Cc: Michael Paquier , pgsql-hackers@postgresql.org, Tom Lane , Smolkin Grigory Subject: Re: race condition in pg_class Message-ID: <20240612193223.fe.nmisch@google.com> References: <20231102030915.d3.nmisch@google.com> <20240512232923.aa.nmisch@google.com> <20240605181706.fe.nmisch@google.com> <20240611021927.30.nmisch@google.com> <20240612175452.de.nmisch@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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 Wed, Jun 12, 2024 at 02:08:31PM -0400, Robert Haas wrote: > On Wed, Jun 12, 2024 at 1:54 PM Noah Misch wrote: > > If I were making a list of changes always welcome post-beta, it wouldn't > > include adding wait event types. But I don't hesitate to add one if it > > unblocks a necessary test for a bug present in all versions. > > However, injection points themselves are not present in all versions, > so even if we invent a new wait-event type, we'll have difficulty > testing older versions, unless we're planning to back-patch all of > that infrastructure, which I assume we aren't. Right. We could put the injection point tests in v18 only instead of v17+v18. I feel that would be an overreaction to a dispute about names that show up only in tests. Even so, I could accept that. > Personally, I think the fact that injection point wait events were put > under Extension is a design mistake that should be corrected before 17 > is out of beta. Works for me. I don't personally have a problem with the use of Extension, since it is a src/test/modules extension creating them. > > Here's what I'm reading for each person's willingness to tolerate each option: > > > > STRATEGY | Paquier | Misch | Haas > > -------------------------------------------------------- > > new "Injection Point" wait type | maybe | yes | yes > > INJECTION_POINT(...) naming | yes | yes | unknown > > isolation spec says event names | yes | no | unknown > > > > Corrections and additional strategy lines welcome. Robert, how do you judge > > the lines where I've listed you as "unknown"? > > I'd tolerate INJECTION_POINT() if we had no other option but I think > it's clearly inferior. Does the last line refer to putting the > specific wait event names in the isolation spec file? If so, I'd also > be fine with that. Yes, the last line does refer to that. Updated table: STRATEGY | Paquier | Misch | Haas -------------------------------------------------------- new "Injection Point" wait type | maybe | yes | yes INJECTION_POINT(...) naming | yes | yes | no isolation spec says event names | yes | no | yes I find that's adequate support for the first line. If there are no objections in the next 24hr, I will implement that.