Thanks for pointing me to this. I also did a search in the archives and found a 2006 thread on TRUNCATE, VACUUM, and ANALYZE privileges:
I'm not seeing much else. As far as I can see, the only demand for using more privilege bits is for VACUUM, ANALYZE, REFRESH, CLUSTER, and REINDEX.
So revised proposal: instead of calling it REFRESH, call it MAINTAIN. Anybody with MAINTAIN permission can do any of those 5 different maintenance actions as if they were the owner of the relation in question.
This uses just 1 bit, leaving 3 more for future expansion, and satisfying all the outstanding requests to allocate privilege bits. I think. That seems like a pretty good deal to me. Also, if a future proposal comes along, it may be appropriate to re-use this new permission at that time, as long as the word "maintain" makes even a little sense as the name in the new context.
We would probably have to apply the same rule to all of these, that the owner can always perform these actions, because of the issue with dumps restored from older databases.
