| From: |
| Tom Lane <tgl-AT-sss.pgh.pa.us> |
| To: |
| Alvaro Herrera <alvherre-AT-2ndquadrant.com> |
| Subject: |
| Re: PostgreSQL pollutes the file system |
| Date: |
| Wed, 27 Mar 2019 10:23:06 -0400 |
| Message-ID: |
| <17471.1553696586@sss.pgh.pa.us> |
| Cc: |
| Tomas Vondra <tomas.vondra-AT-2ndquadrant.com>, "Fred .Flintstone" <eldmannen-AT-gmail.com>, Mark Kirkwood <mark.kirkwood-AT-catalyst.net.nz>, Michael Paquier <michael-AT-paquier.xyz>, Andreas Karlsson <andreas-AT-proxel.se>, Chris Travers <chris.travers-AT-adjust.com>, Tatsuo Ishii <ishii-AT-sraoss.co.jp>, Euler Taveira <euler-AT-timbira.com.br>, Julien Rouhaud <rjuju123-AT-gmail.com>, Postgres hackers <pgsql-hackers-AT-lists.postgresql.org> |
| Archive-link: |
| Article |
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2019-Mar-27, Tomas Vondra wrote:
>> I think the consensus in this thread (and the previous ancient ones) is
>> that it's not worth it. It's one thing to introduce new commands with the
>> pg_ prefix, and it's a completely different thing to rename existing ones.
>> That has inherent costs, and as Tom pointed out the burden would fall on
>> people using PostgreSQL (and that's rather undesirable).
> I thought the consensus was to rename them, and install symlinks to the
> old names.
The question is what's the endgame. We haven't actually fixed the
complained-of confusion problem unless we eventually remove createuser
and dropuser under those names. Are we prepared to force script
breakage of that sort, even over a multi-year deprecation cycle?
(As a comparison point, I note that we still haven't removed the
"postmaster" symlink, though it's been deprecated for at least a
dozen years.)
regards, tom lane
