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 1sqRsU-009oxj-JN for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Sep 2024 06:40:00 +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 1sqRsU-005uAc-14 for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Sep 2024 06:39:58 +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 1sqRsT-005uA1-In for pgsql-hackers@lists.postgresql.org; Tue, 17 Sep 2024 06:39:57 +0000 Received: from dd25110.kasserver.com ([85.13.146.49]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sqRsQ-001ba9-2T for pgsql-hackers@lists.postgresql.org; Tue, 17 Sep 2024 06:39:56 +0000 Received: from [192.168.0.102] (ip-037-201-153-175.um10.pools.vodafone-ip.de [37.201.153.175]) by dd25110.kasserver.com (Postfix) with ESMTPSA id 072F0E1A0159; Tue, 17 Sep 2024 08:39:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=technowledgy.de; s=kas202308201259; t=1726555194; bh=lA12y/HssUbvQ+UTc1HcTWpGPaiLS9F3yU1fPH7G8x8=; h=Date:From:Subject:To:Cc:References:In-Reply-To:From; b=YuqtbbUqicoz95ceIZuza1iViBBmV4bVbLyzPXQ4yY5vlZOR+wTZMY8g1/URFdyCd eZHDWiVbCLincTAxUxhPaUo0AQWehABASt1sOx49VIdmg2JTFt2Ov4ONwoPAFpN64j Lkf3/XQXgzDtHqJaiRMPbLOOKTdAMXFbDkA37ZyxNnVSGp1nVs1wHrTc3gnWQ+x0Zt KkLkthl0zb1l+bD+QkPC8Lb0rJgszyJHMLqtrSepdLJfB1tvNHJAltnUsZVXk/vGiV 4X1yeBu/XQXLcOVMc4nYMejdUuMpy1pEnuguD9CRf2m/4421+KdqzxbicvRu5cl6M/ Y6mXxq5p8HWGQ== Message-ID: Date: Tue, 17 Sep 2024 08:39:53 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Wolfgang Walther Subject: Re: Regression tests fail with tzdata 2024b To: Tom Lane , Sven Klemm Cc: pgsql-hackers@lists.postgresql.org References: <0a997455-5aba-4cf2-a354-d26d8bcbfae6@technowledgy.de> <441306.1726346239@sss.pgh.pa.us> <38e73fef-f19b-4835-b353-a110db6c8318@technowledgy.de> <1043017.1726463364@sss.pgh.pa.us> <1156795.1726499982@sss.pgh.pa.us> <1399310.1726551755@sss.pgh.pa.us> Content-Language: en-US In-Reply-To: <1399310.1726551755@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: / List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tom Lane: >> I was wondering whether the timezone used by pg_regress could be made >> configurable. > > Yes, I understood that you were suggesting that. My point is that > it wouldn't do you any good: you will still have to change any > regression test cases that depend on behavior PST8PDT has/had that > is different from America/Los_Angeles. That being the case, > I don't see much value in making it configurable. Just changing it back to PST8PDT wouldn't really help as Tom pointed out. You'd still get different results depending on which tzdata version you are running with. The core regression tests need to be run with a timezone that tests special cases in the timezone handling code. But that might not be true for extensions - all they want could be a stable output across major and minor versions of postgres and versions of tzdata. It could be helpful to set pg_regress' timezone to UTC, for example? Best, Wolfgang