Re: Removing binaries (was: createlang/droplang deprecated)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removing binaries (was: createlang/droplang deprecated)
Date: 2017-03-19 20:01:38
Message-ID: 31763.1489953698@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andreas Karlsson <andreas(at)proxel(dot)se> writes:
> As for if we should have backwards compatibility for the old names I am
> leaning weakly for providing it in the case of createuser. I can see end
> users being pissed off that the createuser command is suddenly gone
> without any warning when they upgrade. On the flip side I have no idea
> how much work it would be to maintain those legacy names.

It seems reasonably trivial to me as far as the code goes --- just
create a symlink during installation. (On Windows I suppose we'd have
to make a second physical copy, but these files are not so large that
that seems unacceptable.) It might be more work on the documentation
side, depending on whether you wanted two copies of the man page or
not. I see that postmaster's man page pretty much just points to
postgres, so it seems like we could do that for these scripts too.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-03-19 20:13:17 Re: Removing binaries (was: createlang/droplang deprecated)
Previous Message Alvaro Herrera 2017-03-19 20:00:07 Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless)