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 1jS6IL-0001u5-3r for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Apr 2020 21:55:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jS6IK-0007j3-0x for pgsql-hackers@arkaria.postgresql.org; Fri, 24 Apr 2020 21:55:36 +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 1jS6IJ-0007iw-Qf for pgsql-hackers@lists.postgresql.org; Fri, 24 Apr 2020 21:55:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jS6IH-0002tC-Om for pgsql-hackers@lists.postgresql.org; Fri, 24 Apr 2020 21:55:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 03OLtWBx021043; Fri, 24 Apr 2020 17:55:32 -0400 From: Tom Lane To: =?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= cc: PostgreSQL Hackers Subject: Re: Anybody want to check for Windows timezone updates? In-reply-to: References: <5752.1587740484@sss.pgh.pa.us> Comments: In-reply-to =?UTF-8?Q?Juan_Jos=C3=A9_Santamar=C3=ADa_Flecha?= message dated "Fri, 24 Apr 2020 19:42:47 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21041.1587765332.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 24 Apr 2020 17:55:32 -0400 Message-ID: <21042.1587765332@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk =3D?UTF-8?Q?Juan_Jos=3DC3=3DA9_Santamar=3DC3=3DADa_Flecha?=3D writes: > Please find attached the output from Windows Server 2019. Thanks! That was a bit tedious --- I suppose it's not quite worth automating further, but I did make some effort to remove the cross-version formatting hazards in that table. Could you verify that there are no complaints now with HEAD? I might've fat-fingered something. regards, tom lane