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 1ijO2o-0006kb-LS for pgsql-bugs@arkaria.postgresql.org; Mon, 23 Dec 2019 13:46:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ijO2l-0003Q8-BU for pgsql-bugs@arkaria.postgresql.org; Mon, 23 Dec 2019 13:46:43 +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 1ijO2l-0003Q1-3F for pgsql-bugs@lists.postgresql.org; Mon, 23 Dec 2019 13:46:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ijO2h-0008Bi-2w for pgsql-bugs@lists.postgresql.org; Mon, 23 Dec 2019 13:46:42 +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 xBNDkX2d018082; Mon, 23 Dec 2019 08:46:33 -0500 From: Tom Lane To: indreek@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16178: DROP LANGUAGE plpythonu; doesn't actually drop language. In-reply-to: <16178-d556fe3d69ee5271@postgresql.org> References: <16178-d556fe3d69ee5271@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 23 Dec 2019 09:23:46 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18080.1577108793.1@sss.pgh.pa.us> Date: Mon, 23 Dec 2019 08:46:33 -0500 Message-ID: <18081.1577108793@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > [ assorted manual manipulation of plpythonu language ] > Doing the same thing with extensions works fine. This is in the category of "if it breaks you get to keep both pieces". We don't really support installing PLs via any other means except their extensions anymore. In the case at hand, I believe what's biting you is that CREATE LANGUAGE auto-created the language's support functions (because the alternative would be to fail entirely) but DROP LANGUAGE didn't drop them. Nobody is going to work on changing that. The actual likely future direction of development is for the auto-creation behavior to go away [1], so there would hardly be any point in hacking up DROP LANGUAGE. I'd suggest manually dropping the support functions (plpython_call_handler, plpython_inline_handler, plpython_validator) to get back to an upgradable state. Or you could install plpython2 in the new installation. regards, tom lane [1] https://www.postgresql.org/message-id/flat/5889.1566415762%40sss.pgh.pa.us