Corey,
* Corey Huinker (corey.huin...@gmail.com) wrote:
> I think allowing users to receive and send serialized relacl values (which
> is what I *think* you're asking about here) is only slightly less icky, and
That isn't actually what I was suggesting.
> presents a backward compatibility issue.
Robert,
* Robert Haas (robertmh...@gmail.com) wrote:
> On Wed, Nov 9, 2016 at 2:54 PM, Corey Huinker wrote:
> > 3. The operation is judged to have succeeded if at least one permission is
> > granted, or NO grants failed (i.e. there was nothing to grant).
>
> Allow me to be skeptical. If a user
On Wed, Nov 9, 2016 at 2:54 PM, Corey Huinker wrote:
> 3. The operation is judged to have succeeded if at least one permission is
> granted, or NO grants failed (i.e. there was nothing to grant).
Allow me to be skeptical. If a user types INSERT INTO blah VALUES
(...), (...), (...) should we chan
>
> > SET relacl = ( SELECT relacl FROM pg_class
> >WHERE oid = 'foo'::regclass)
> > WHERE oid = 'dummy'::regclass;
>
> Yikes, let's not suggest folks go updating catalog tables, ever, please.
> :)
>
Glad you find that as icky as I do.
> Should we have a way for users to
Robert Haas writes:
> On Tue, Nov 8, 2016 at 9:48 AM, Stephen Frost wrote:
>> Second, as always, what's the syntax going to actually be? I don't
>> think GRANT SAME PERMISSIONS is going to work out too well in the
>> parser, and it seems a bit grotty to me anyway. I do think this should
>> be a
On Tue, Nov 8, 2016 at 9:48 AM, Stephen Frost wrote:
> Second, as always, what's the syntax going to actually be? I don't
> think GRANT SAME PERMISSIONS is going to work out too well in the
> parser, and it seems a bit grotty to me anyway. I do think this should
> be associated with GRANT rather
Corey,
* Corey Huinker (corey.huin...@gmail.com) wrote:
> Craig's post yesterday about exposing syntax for disabling indexes reminded
> me of another feature I think we're lacking in areas where we have to do
> table management.
>
> The issue is to create a *something* that has the exact permissi
Craig's post yesterday about exposing syntax for disabling indexes reminded
me of another feature I think we're lacking in areas where we have to do
table management.
The issue is to create a *something* that has the exact permissions of
another *something*. Usually it's creating a table related t