Re: change alter user to be a true alias for alter role

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jov <amutu(at)amutu(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: change alter user to be a true alias for alter role
Date: 2014-06-19 17:18:48
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Jov <amutu(at)amutu(dot)com> writes:
> the doc say:
>> ALTER USER is now an alias for ALTER ROLE<>

> but alter user lack the following format:
> ...

If we're going to have a policy that these commands be exactly equivalent,
it seems like this patch is just sticking a finger into the dike. It does
nothing to prevent anyone from making the same mistake again in future.

What about collapsing both sets of productions into one, along the lines

role_or_user: ROLE | USER;

ALTER role_or_user RoleId opt_in_database SetResetClause

(and similarly to the latter for every existing ALTER ROLE variant).

Because MAPPING is an unreserved keyword, I think that this approach
might force us to also change ALTER USER MAPPING to ALTER role_or_user
MAPPING, which is not contemplated by the SQL standard. But hey,
it would satisfy the principle of least surprise no? Anyway we don't
have to document that that would work.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2014-06-19 17:20:33 Re: Minmax indexes
Previous Message Tom Lane 2014-06-19 17:01:34 Re: Crash on backend exit w/ OpenLDAP [2.4.24, 2.4.31]