Re: Extra functionality to createuser

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Christopher Browne <cbbrowne(at)gmail(dot)com>, Sameer Thakur <samthakur74(at)gmail(dot)com>, PostgreSQL Mailing Lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extra functionality to createuser
Date: 2013-12-08 04:39:20
Message-ID: CAA4eK1JLnSnSXEsP3hJ9cRAeNEq9r7os6bmKsrHmt0gW1-2Jyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 6, 2013 at 10:31 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On Wed, 2013-11-20 at 11:23 -0500, Christopher Browne wrote:
>> I note that similar (with not quite identical behaviour) issues apply
>> to the user name. Perhaps the
>> resolution to this is to leave quoting issues to the administrator.
>> That simplifies the problem away.
>
> How about only one role name per -g option, but allowing the -g option
> to be repeated?

I think that might simplify the problem and patch, but do you think
it is okay to have inconsistency
for usage of options between Create User statement and this utility?

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message huaicheng Li 2013-12-08 06:55:57 About shared cache invalidation mechanism
Previous Message Amit Kapila 2013-12-08 04:22:39 Re: [bug fix] pg_ctl fails with config-only directory