Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pINeH-0000uV-Ii for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Jan 2023 05:39:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pINeF-0003BF-Hv for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Jan 2023 05:39:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pINeF-0003B6-1P for pgsql-hackers@lists.postgresql.org; Thu, 19 Jan 2023 05:39:39 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pINe7-0007WR-7Y for pgsql-hackers@postgresql.org; Thu, 19 Jan 2023 05:39:37 +0000 Received: from [192.168.28.53] (cyclops.postgrespro.ru [93.174.131.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id 1D2B521C74B7; Thu, 19 Jan 2023 08:39:28 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1674106768; bh=z474CLJ6KAxIVjod8vY4HuKdyO3T9OTh6av+6PP+n0Q=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=aqkzEpYhvnzte/X4HV50eZu19nTOsaLFDxlMMi1R32FAL6jkgfCxCVLs6+VSujt9m wBtXMSDFfb0vNrbVf7qbHHyAuMLLmF63sRuxyhOdkRIbuE3a2qxpabX+/LFzxdxYbc 8WquIBinnOixnHK6RDGYBR8wplCl1jkMpXzqc8x8= Message-ID: <72017e35-9b16-9223-d785-3e5a452f186a@postgrespro.ru> Date: Thu, 19 Jan 2023 10:39:27 +0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.0 Subject: Re: [PATCH] random_normal function To: Tom Lane Cc: Dean Rasheed , Fabien COELHO , Michael Paquier , Justin Pryzby , pgsql-hackers@postgresql.org, Paul Ramsey References: <20221208224623.GQ27893@telsasoft.com> <20221231035804.GJ1153@telsasoft.com> <1682143.1672713508@sss.pgh.pa.us> <1776287.1672764097@sss.pgh.pa.us> <3983784.1673223640@sss.pgh.pa.us> <3996998.1673230641@sss.pgh.pa.us> <4173840.1673290336@sss.pgh.pa.us> Content-Language: en-US From: Andrey Lepikhov Organization: Postgres Professional In-Reply-To: <4173840.1673290336@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/9/23 23:52, Tom Lane wrote: > BTW, if this does bring the probability of failure down to the > one-in-a-billion range, I think we could also nuke the whole > "ignore:" business, simplifying pg_regress and allowing the > random test to be run in parallel with others. With 'ignore' option we get used to cover by tests some of the time dependent features, such as "statement_timeout", "idle_in_transaction_session_timeout", usage of user timeouts in extensions and so on. We have used the pg_sleep() function to interrupt a query at certain execution phase. But on some platforms, especially in containers, the query can vary execution time in so widely that the pg_sleep() timeout, required to get rid of dependency on a query execution time, has become unacceptable. So, the "ignore" option was the best choice. For Now, Do we only have the "isolation tests" option to create stable execution time-dependent tests now? Or I'm not aware about some test machinery? -- Regards Andrey Lepikhov Postgres Professional