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 1n81cZ-0001oF-8G for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Jan 2022 15:02:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n81cY-0004jm-2q for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Jan 2022 15:02:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81cX-0004hW-OX for pgsql-hackers@lists.postgresql.org; Thu, 13 Jan 2022 15:02:33 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81cO-0004eM-RB for pgsql-hackers@postgresql.org; Thu, 13 Jan 2022 15:02:33 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 011BC32009E8; Thu, 13 Jan 2022 10:02:19 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 13 Jan 2022 10:02:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm1; bh=Ixhn854Ql8EkD5z4hLVgRUHYKz6DPHlIUFHrjucPR aU=; b=DoJ/wCHdQj87rQ8dvbZ29DggiqidTA4TWhsjY3NMVRXtSCmqs69MPDfLE +7gCSwZgnE7aJFwY39ahcaSatC+ayB1u6uV9osfDCxCGGqPJKJRkki2BOgX6oimS OxFf8DYt/rgJ29D3yrwOmc+z63ZD1ebaO/wgYWNDYBUV9gJjKWBSrltt7iSCSgwO kgZuPbHsp38CdYPGQEg3UKGNs2MWhoq/EW+xPkDMDFvhU0vsaFXsSp/z7NZasR5O GpI6UOkbgKgIX3G/tnrS3vFAIYBNhnH602J07rS6oz1ntephRiUxJbTVMyxlOaOa CEHIjBvFKkSFFKnrVm/dWXTscuObw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrtdefgdejudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 13 Jan 2022 10:02:16 -0500 (EST) Message-ID: <3ac7b6b7-1187-e912-a689-cab59d67aeb5@enterprisedb.com> Date: Thu, 13 Jan 2022 16:02:14 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: Time to drop plpython2? Content-Language: en-US To: Tom Lane Cc: Andres Freund , pgsql-hackers@postgresql.org References: <20211031184548.g4sxfe47n2kyi55r@alap3.anarazel.de> <08a65981-7fec-1b9b-4061-6e3086c05914@enterprisedb.com> <3fc1211d-960b-4b2f-3e96-a6099db847fc@enterprisedb.com> <20211104195443.dystyijvufveikcp@alap3.anarazel.de> <85eb62cd-76f3-d01f-79ef-144173c16edc@enterprisedb.com> <2057149.1636943071@sss.pgh.pa.us> <20211115170632.buql3valv5mlnbni@alap3.anarazel.de> <2138217.1636996791@sss.pgh.pa.us> <20211115181246.gtnaeim6fo3vjb7c@alap3.anarazel.de> <2142324.1637000302@sss.pgh.pa.us> <21ad7747-d4de-e7b6-7864-be07929fb067@enterprisedb.com> <2594342.1641917185@sss.pgh.pa.us> <59eec9e5-f62a-4aeb-4cd6-ee5fddc2d6b4@enterprisedb.com> <3027819.1642013355@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <3027819.1642013355@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 12.01.22 19:49, Tom Lane wrote: > Anyway, getting back to the point: I think we should notify the > owners ASAP and set a 30-day deadline. We should try to get this > done before the March CF starts, so it's too late for a 60-day > grace period. In any case, the worst-case scenario for an owner > is to disable --with-python until they have time to do an upgrade, > so it doesn't seem like a month is a big problem. Sure, let's do that. I don't have a buildfarm animal these days, so I'm not on that list, so it would be great if you could do that