Re: initdb createuser commands

Adrian, I like the idea of teaching the appropriate SQL to achieve the
same thing. It makes a lot of sense, it's a pity the majority of
documentation doesn't do this.

John, if you read my earlier email you'd see that I proposed including
deprecation notices and aliasing the commands. I appreciate the need
for existing documentation to continue being relevant.

Melvin, I think you are blowing things out of proportion. I didn't
propose to rename the commands entirely such as "createuser" to
"prepareaccount". But, I think having "pg_createuser" or, preferrably,
"pg createuser". It's tidier, respectful of a limited global namespace
of command names, and potentially easier for everyone.

Gavin, I appreciate this is a low priority. But I think it's also
really easy to do by someone who is experienced. Perhaps a day or two
of work? So, it's low priority but also not that difficult and it's an
opportunity to improve the command line experience in a very
fundamental way for new users and experienced users alike.

In my mind, making Postgresql approachable by new users should be a
high priority.

This is really just my 2c, I'd be happy to submit a PR but can you
confirm intention to work on it to acceptance? Otherwise I'm just
wasting everyone's time including my own :)

On 30 October 2016 at 13:31, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> wrote:
> On 30/10/16 11:25, John R Pierce wrote:
>>
>> On 10/29/2016 3:02 PM, Samuel Williams wrote:
>>>
>>> FYI,https://wiki.archlinux.org/index.php/PostgreSQL mentions initdb,
>>> createuser, createdb and several others. I think my suggestion is
>>> still relevant and something that would improve the system for new
>>> users
>>
>>
>> and it would break it for the existing community that has up to 20 years
>> of experience with it, as well as breaking virtually all existing
>> documentation, books, howto articles, etc, including the one you linked.
>>
>>
> I think it would be good to have all the postgresql utilities prefixed by
> pg_ to keep them together, but have aliases so existing scripts &
> documentation (especially 3rd party) were still relevant.
>
> However, I wouldn't consider it the highest priority.
>
>
> Cheers,
> Gavin
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general