From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Samuel Williams <space(dot)ship(dot)traveller(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: initdb createuser commands |
Date: | 2016-10-30 15:07:38 |
Message-ID: | 1622f00d-8a70-0522-eecb-ce378c19490d@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/30/2016 02:19 AM, Samuel Williams wrote:
> John - that's an interesting example. If it's that easy, why isn't
> that the approach given in tutorials and other documentation? What was
> the motivation for the createuser command?
psql was less user friendly in the past?
Compare:
https://www.postgresql.org/docs/7.1/static/app-psql.html
to
https://www.postgresql.org/docs/9.5/static/app-psql.html
>
> On 30 October 2016 at 20:20, John R Pierce <pierce(at)hogranch(dot)com> wrote:
>> On 10/30/2016 12:15 AM, Samuel Williams wrote:
>>>
>>> But, I think having "pg_createuser" or, preferrably, "pg createuser".
>>
>>
>> psql -c "create user ...."
>>
>>
>>
>> --
>> john r pierce, recycling bits in santa cruz
>>
>>
>>
>> --
>> 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
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-10-30 15:30:42 | Re: initdb createuser commands |
Previous Message | Melvin Davidson | 2016-10-30 14:11:39 | Re: Way to quickly detect if database tables/columns/etc. were modified? |