> On Sep 7, 2022, at 4:09 PM, Stephen Frost <sfr...@snowman.net> wrote: > > Calling this a redesign is over-stating things, imv … and I’d much rather > have the per-relation granularity than predefined roles for this, so there is > that to consider too, perhaps. Ok, now I'm a bit lost. If I want to use Nathan's feature to create a role to vacuum and analyze my database on a regular basis, how does per-relation granularity help me? If somebody creates a new table and doesn't grant those privileges to the role, doesn't that break the usage case? To me, per-relation granularity sounds useful, but orthogonal, to this feature. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
- Re: predefined role(s) for VACUUM and ANALYZE Stephen Frost
- Re: predefined role(s) for VACUUM and ANALYZE Nathan Bossart
- Re: predefined role(s) for VACUUM and ANALYZE Robert Haas
- Re: predefined role(s) for VACUUM and ANALYZE Stephen Frost
- Re: predefined role(s) for VACUUM and ANALYZE Robert Haas
- Re: predefined role(s) for VACUUM and ANA... Nathan Bossart
- Re: predefined role(s) for VACUUM an... Stephen Frost
- Re: predefined role(s) for VACUU... Nathan Bossart
- Re: predefined role(s) for V... Stephen Frost
- Re: predefined role(s) for V... Mark Dilger
- Re: predefined role(s) for V... Nathan Bossart
- Re: predefined role(s) for V... Nathan Bossart
- Re: predefined role(s) for V... Robert Haas
- Re: predefined role(s) for V... Nathan Bossart
- Re: predefined role(s) for V... Michael Paquier
- Re: predefined role(s) for V... Nathan Bossart
- Re: predefined role(s) for V... Nathan Bossart
- Re: predefined role(s) for V... Nathan Bossart
- Re: predefined role(s) for V... Michael Paquier
- Re: predefined role(s) for V... Nathan Bossart