| From: | Robins Tharakan <tharakan(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: CREATE OPERATOR query |
| Date: | 2013-05-22 21:33:54 |
| Message-ID: | CAEP4nAxvejtVZq+WNVq14LkY0Lc=E-8ANGiHvWQwixq2thqhHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Makes perfect sense. Thanks and appreciate a prompt response.
Would update the tests accordingly.
--
Robins Tharakan
On 22 May 2013 09:03, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Robins Tharakan escribió:
> > Yes, but the documentation states that EXECUTE permission for the
> function
> > is required to even CREATE the operator.
>
> What I mean is that your new role still has said permission through
> PUBLIC (a pseudo-role which is automatically granted to all other roles
> and cannot be revoked), even if you revoke it directly.
>
> --
> Álvaro Herrera http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erwin Brandstetter | 2013-05-24 18:07:52 | Contradicting information for DEFERRABLE constraints |
| Previous Message | Josh Kupershmidt | 2013-05-22 12:55:21 | Re: moving documentation to XML |