Hey,
This does work, but as I'm using DEFAULT PRIVs to give access to tables it becomes a (the only) step which can't be done at schema creation time and has to be done at data insertion time.
It feels to me that ALTER DEFAULT PRIVILEGES should be extended to support large objects (either by default from the table permissions or as a new GRANT option). Thoughts on this?
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
______________________________________
On Wed, Sep 11, 2013 at 6:40 PM, Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx> wrote:
On Wed, Sep 11, 2013 at 10:19 AM, James Sewell <james.sewell@xxxxxxxxxxxx> wrote:
Hello all,I have a table which makes use of pg_largeobjects. I am inserting rows into the table as user1. If I connect to the database as user2 I can SELECT data, but can not open the large object for reading (user1 can do this). I don't want to set lo_compat_privileges as then user3 (who can't SELECT from the services tables) would be able to read the large object.GRANT SELECT,UPATE ON LARGE OBJECT to user2;Will this work...
The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.
