| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Allow CURRENT_ROLE in GRANTED BY |
| Date: | 2020-06-24 06:35:58 |
| Message-ID: | f2feac44-b4c5-f38f-3699-2851d6a76dc9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I was checking some loose ends in SQL conformance, when I noticed: We
support GRANT role ... GRANTED BY CURRENT_USER, but we don't support
CURRENT_ROLE in that place, even though in PostgreSQL they are
equivalent. Here is a trivial patch to add that.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Allow-CURRENT_ROLE-in-GRANTED-BY.patch | text/plain | 1.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-06-24 06:39:26 | should libpq also require TLSv1.2 by default? |
| Previous Message | Michael Paquier | 2020-06-24 06:16:49 | Re: Update InsertPgAttributeTuple comment to match new signature |