Fix up some loose ends for CURRENT_USER as RoleSpec
Alvaro Herrera <alvherre@alvh.no-ip.org>
Fix up some loose ends for CURRENT_USER as RoleSpec In commit 31eae6028eca4, some documents were not updated to show the new capability; fix that. Also, the error message you get when CURRENT_USER and SESSION_USER are used in a context that doesn't accept them could be clearer about it being a problem only in those contexts; so add the word "here". Author: Kyotaro HORIGUCHI His patch submission also included changes to GRANT/REVOKE, but those seemed more controversial, so I left them out. We can reconsider these changes later.
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/ref/alter_policy.sgml | modified | +1 −1 |
| doc/src/sgml/ref/create_policy.sgml | modified | +1 −1 |
| doc/src/sgml/ref/create_tablespace.sgml | modified | +1 −1 |
| doc/src/sgml/ref/drop_owned.sgml | modified | +1 −1 |
| doc/src/sgml/ref/reassign_owned.sgml | modified | +2 −1 |
| src/backend/parser/gram.y | modified | +2 −2 |
| src/test/regress/expected/rolenames.out | modified | +2 −2 |