Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdzhT-0001PN-Kk for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Jun 2019 16:14:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hdzhS-00066k-2g for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Jun 2019 16:14:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdzhR-00066F-PV for pgsql-hackers@lists.postgresql.org; Thu, 20 Jun 2019 16:14:09 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdzhP-0000AN-F9 for pgsql-hackers@postgresql.org; Thu, 20 Jun 2019 16:14:09 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id A92C14A8; Thu, 20 Jun 2019 12:14:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 20 Jun 2019 12:14:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=Htbr5eQx7nTN/EV5+OHLuCNGQDr s+g6br3UqqMHw7/8=; b=3YfCiklNBT0YQtuSIhIvP+rGWFP+AWKF/uv5N+2TWns Yu36kPBpjmHLU/AvRpRHhx/9nP92cpXLVXQcBEU+qeES7dpTMYZGRKwp9fXb0fwA ZRTnCFq20No/TK+XNKk2fWuSICZM+3O8FUAC57aJImM3sPL9RqPY4EIkxFUp7kVv 4ofbG/taWB/UM3jOubLiwQR20b6uydRtqLNUXu4xggjq0S2XPBW+8fsD5KCAAGVk lsvrrmpZGOG6VURx5b+JPSGLjBRDvH9nYNPuHxLQD29wJf7VazdT4ZN7Av8zRNYx P9GbXnaiOZCM7Y2/2Jsu9KSfenxJBBfVxbj2I9xjgew== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Htbr5e Qx7nTN/EV5+OHLuCNGQDrs+g6br3UqqMHw7/8=; b=UXs7sDs03FGBJe5nLuMJWw 6jz/SeY2C/l5ZPYvJX2BGIJoFs1c+Hg5CGEo8A1dvRoCvpOmVFinUGy5ucUEhswS fdSmTFSg6/rlIH1dExQ8mwh1geRU5pjUNYB15SHzkw+/ozxDy3U+LOn25Gq+UUW2 JHLKn7gEcI1e2legPxo49OCMubhPeHgcPSTEe+0saYHjFwrSap84Io/E9IRGtwnr y2pD2mEQSspdCTcKCRe9Hloj2ZaPGjhXR0qB9xif+T3Y3oX/wgCe1G6pK0y/mX59 uYeDLrd6YkmQqC6yDvppi2iJgwTXaL//7soOTq55xeqJoyD/Z+CFpQ8jM+iP5fFA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrtdeggddutdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucfkphepie ejrdduiedtrddvudekrddvfeejnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgv shesrghnrghrrgiivghlrdguvgenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from intern.anarazel.de (c-67-160-218-237.hsd1.ca.comcast.net [67.160.218.237]) by mail.messagingengine.com (Postfix) with ESMTPA id 4ACEC8005C; Thu, 20 Jun 2019 12:14:02 -0400 (EDT) Date: Thu, 20 Jun 2019 09:14:00 -0700 From: Andres Freund To: Robert Haas Cc: Stephen Frost , Tom Lane , Andrew Gierth , Christoph Berg , PostgreSQL Hackers Subject: Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) Message-ID: <20190620161400.6wtuybv64ihnfy6d@alap3.anarazel.de> References: <875zp74zpf.fsf@news-spur.riddles.org.uk> <871rzv4yes.fsf@news-spur.riddles.org.uk> <20190617173943.z3ttxqenbcwrlag4@alap3.anarazel.de> <20190617183458.GG2480@tamriel.snowman.net> <20190617183828.hj7ci362zbxd4nax@alap3.anarazel.de> <20190617184053.GI2480@tamriel.snowman.net> <25314.1560980148@sss.pgh.pa.us> <20190620125211.GX2480@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2019-06-20 12:02:30 -0400, Robert Haas wrote: > On Thu, Jun 20, 2019 at 8:52 AM Stephen Frost wrote: > > I don't want to come across as implying that I'm saying what was done > > was 'fine', or that we shouldn't be having this conversation, I'm just > > trying to figure out how we can frame it in a way that we learn from it > > and work to improve on it for the future, should something like this > > happen again. > > I agree that it's a difficult situation. I do kind of wonder whether > we were altogether overreacting. If we had shipped it as it was, > what's the worst thing that would have happened? I think it's not good, but also nothing particularly bad came out of it. I don't think we should try to set up procedures for future occurances, and rather work/plan on that not happening very often. Greetings, Andres Freund