Re: BUG #12939: GRANT ALL ON ALL SEQUENCES doesn't work for sequences not yet existing - Mailing list pgsql-bugs

From Hale, Tyler
Subject Re: BUG #12939: GRANT ALL ON ALL SEQUENCES doesn't work for sequences not yet existing
Date
Msg-id 7123D00A1041B64F962A9AA1E8F045C503DCBB1221@KDCPEXCMB03.cof.ds.capitalone.com
Whole thread Raw
In response to Re: BUG #12939: GRANT ALL ON ALL SEQUENCES doesn't work for sequences not yet existing  (Stephen Frost <sfrost@snowman.net>)
List pgsql-bugs
Thanks for the insight Stephen.  Do you know if this type of functionality =
is only limited to sequences or all types of database objects?  I am relati=
vely new to Postgres and am trying to come up with rules/best practices for=
 my team to use when deploying new structures on Postgres.

Thanks,
Tyler

-----Original Message-----
From: Stephen Frost [mailto:sfrost@snowman.net] =

Sent: Wednesday, April 01, 2015 5:08 PM
To: Hale, Tyler
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #12939: GRANT ALL ON ALL SEQUENCES doesn't work for=
 sequences not yet existing

Tyler,

* tyler.hale@capitalone.com (tyler.hale@capitalone.com) wrote:
> Running a GRANT ALL ON ALL SEQUENCES IN PUBLIC SCHEMA doesn't work =

> when the sequence is created after running the GRANT statement =

> regardless of whether the sequence was created implicitly or explicitly.

GRANT ALL only operates against objects which already exist.

If you wish to set default privileges, use ALTER DEFAULT PRIVILEGES.
Those will then apply for newly created objects.

    Thanks!

        Stephen
________________________________________________________

The information contained in this e-mail is confidential and/or proprietary=
 to Capital One and/or its affiliates. The information transmitted herewith=
 is intended only for use by the individual or entity to which it is addres=
sed.  If the reader of this message is not the intended recipient, you are =
hereby notified that any review, retransmission, dissemination, distributio=
n, copying or other use of, or taking of any action in reliance upon this i=
nformation is strictly prohibited. If you have received this communication =
in error, please contact the sender and delete the material from your compu=
ter.

pgsql-bugs by date:

Previous
From: robert.uradin@gmail.com
Date:
Subject: BUG #12950: Update problem
Next
From: Peter Slavov
Date:
Subject: Re: BUG #12910: Memory leak with logical decoding