Re: [HACKERS] createlang/droplang deprecated - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] createlang/droplang deprecated
Date
Msg-id CA+TgmoYVKypMxmny7UfP-RoF0+OyJCr1M-ieJ19a6AnXwYLxDg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] createlang/droplang deprecated  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] createlang/droplang deprecated  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Sat, Mar 18, 2017 at 11:29 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>>> 2017-03-18 14:00 GMT+01:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
>>>> I just noticed that createlang and droplang have been listed as
>>>> deprecated since PG 9.1.
>>>> Do we dare remove them?
>
>> (I'd extend it to all the non-prefixed pg binaries, but let's open that can
>> of worms right now, one thing at a time)
>
> To my mind, these two and createuser/dropuser are the only really serious
> namespacing problems among our standard binaries.  The ones with names
> ending in "db" don't seem likely to cause huge confusion.  I suppose that
> if we were naming it today, "psql" wouldn't get that name; but the chances
> of renaming that one are certainly zero, namespace conflict or no.
>
> But createuser/dropuser are a real problem, because they certainly could
> be mistaken for system-level utilities.

Well, let's do one thing at a time.  I think it'd be fine to drop
createlang and droplang; we can discuss other things on other threads.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: [HACKERS] \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] New CORRESPONDING clause design