Re: alter user/role CURRENT_USER - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: alter user/role CURRENT_USER
Date
Msg-id 1414507954.96166.YahooMailNeo@web122301.mail.ne1.yahoo.com
Whole thread Raw
In response to Re: alter user/role CURRENT_USER  (Stephen Frost <sfrost@snowman.net>)
Responses Re: alter user/role CURRENT_USER
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> wrote:

> You can still double-quote reserved words and use them in general.  What
> we're talking about here are cases where a word can't be used even if
> it's double-quoted, and we try really hard to keep those cases at an
> absolute minimum.  We should also really be keeping a list of those
> cases somewhere, now that I think about it..

It is very important that a quoted identifier not be treated as a
keyword.  I would be very interested in seeing that list, and in
ensuring that it doesn't get any longer.

> I agree that we should probably seperate the concerns here.  Personally,
> I like the idea of being able to say "CURRENT_USER" in utility commands
> to refer to the current user where a role would normally be expected, as
> I could see it simplifying things for some applications, but that's a
> new feature and independent of making role-vs-user cases more
> consistent.

Yeah, let's not mix those in the same patch.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: [WIP Patch] Using 128-bit integers for sum, avg and statistics aggregates
Next
From: Robert Haas
Date:
Subject: Re: WIP: Access method extendability