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 1s4SrV-004ECE-QX for pgsql-hackers@arkaria.postgresql.org; Tue, 07 May 2024 22:00:37 +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 1s4SrS-005Qm6-7m for pgsql-hackers@arkaria.postgresql.org; Tue, 07 May 2024 22:00:35 +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.94.2) (envelope-from ) id 1s4SrR-005QkR-CB for pgsql-hackers@lists.postgresql.org; Tue, 07 May 2024 22:00:34 +0000 Received: from mail-yb1-xb33.google.com ([2607:f8b0:4864:20::b33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s4SrL-001w2h-60 for pgsql-hackers@postgresql.org; Tue, 07 May 2024 22:00:32 +0000 Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-dcd7c526cc0so4186351276.1 for ; Tue, 07 May 2024 15:00:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1715119226; x=1715724026; darn=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=lMq18BLNaXvWcVGlN1B5EHcRnyB+Go4mLTAxn9JSMXI=; b=WTJ5vHutKI3UXeJt5QTqb4fzraVAeIDigLjSDZyYgwjsVnD97VhfTs6JwYKnlSM7Xt QxxZg8gUrjZxUB8gxaa2LKBpOSDPor2csA+xoSYhhWo7L8fymmQXH3RNAnajd0cTTcZ5 o46we2k0B+/BrSQQRqE1j9X6IEP9q1/Wz+68g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715119226; x=1715724026; 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=lMq18BLNaXvWcVGlN1B5EHcRnyB+Go4mLTAxn9JSMXI=; b=o5Lr60u903fA2xsTiAk/6dSkGg0igJ7u3GqbWDlEhdzuZfIyjVhXZeIuJ7Q75SskbU RhPMNB4UiEn2jIRENcom9J8SRiUGgnBCTtAEmJFDIZeu7QaAtJQ7Zk0D434tlgO/HpKA cWR0Qp+lgND6SG9ncZn4+mam/TKf8pkDc64ShBea2s1XyvtbjMitRBJ8yXtKknr+E4w9 ZreuD8Htc2NV5lcX5T76ZTEFfdIWn8odjSJ2CetjRQzknDzrZ7HP7lSMQHOOsNwoAuTx qxv6LE+eVkOU9Fdy7VaeDeDNlO1Hag/SGldaD3lusb5OPUgjJnmQe+r+eTgdqnSMZr+A qRTg== X-Forwarded-Encrypted: i=1; AJvYcCVNZ4p7XrwHSRrQDIH2JZExXONyiX7hRImS5Q1amfUcrXRoij66V+hOQXYQ9OmwZ/iGJquzQgZP4sE8UnUhjfPRRWUiA9haO9YlO/r0 X-Gm-Message-State: AOJu0YyiUyt/dm9nwdpSzplWFlIMKa6vovBh2ZNcgjhiJfojwVAtmKZM JttyQq6MHg/w0NqsDVdVbxCLpiqnfjIir2auhS+pamCke+klvZKG/s7xbH9Kxw== X-Google-Smtp-Source: AGHT+IEJK7w4nFRBcMMTWDNCKij+gsHSy37TJH7javYyKGb9OCaCowRaI541BGoiqhbf/aDl1nCnIA== X-Received: by 2002:a05:6902:56e:b0:de8:c4d7:97db with SMTP id 3f1490d57ef6-debb9cfcbc4mr1059147276.22.1715119226220; Tue, 07 May 2024 15:00:26 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id p139-20020a25d891000000b00de50124defcsm2819030ybg.39.2024.05.07.15.00.24 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 May 2024 15:00:25 -0700 (PDT) Date: Tue, 7 May 2024 15:00:23 -0700 From: Noah Misch To: Michael Paquier Cc: Heikki Linnakangas , Tom Lane , pgsql-hackers Subject: Re: Weird test mixup Message-ID: <20240507220023.47.nmisch@google.com> References: <20240501231214.40@rfd.leadboat.com> <20240502193555.a1.nmisch@google.com> <20240506212324.2e.nmisch@google.com> <20240507185310.d3@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240507185310.d3@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 Tue, May 07, 2024 at 11:53:10AM -0700, Noah Misch wrote: > On Tue, May 07, 2024 at 10:17:49AM +0900, Michael Paquier wrote: > > Overall, this switches from one detach behavior to a different one, > > Can you say more about that? The only behavior change known to me is that a > given injection point workload uses more of INJ_MAX_CONDITION. If there's > another behavior change, it was likely unintended. I see patch inplace030-inj-exit-race-v1.patch does not fix the race seen with repro-inj-exit-race-v1.patch. I withdraw inplace030-inj-exit-race-v1.patch, and I withdraw the above question. > To reproduce, apply [repro-inj-exit-race-v1.patch] to add > sleeps, and run: > > make -C src/test/modules/gin installcheck USE_MODULE_DB=1 & sleep 2; make -C contrib/intarray installcheck USE_MODULE_DB=1 > > Separately, I see injection_points_attach() populates InjectionPointCondition > after InjectionPointAttach(). Shouldn't InjectionPointAttach() come last, to > avoid the same sort of race? I've not tried to reproduce that one.