Re: add \dpS to psql
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Pavel Luzanov <p.luzanov@postgrespro.ru>
Cc: Isaac Morland <isaac.morland@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Nathan Bossart <nathandbossart@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org
Date: 2022-12-08T11:35:28Z
Lists: pgsql-hackers
On 2022-Dec-08, Pavel Luzanov wrote: > For the complete picture, I tried to see what other actions with the table > could *potentially* be considered as maintenance. > Here is the list: > > - create|alter|drop on extended statistics objects > - alter table|index alter column set statistics > - alter table|index [re]set (storage_parameters) > - alter table|index set tablespace > - alter table alter column set storage|compression > - any actions with the TOAST table that can be performed separately from the > main table Well, I can't see that any of these is valuable to grant separately from the table's owner. The maintenance ones are the ones that are interesting to run from a database-owner perspective, but these ones do not seem to need that treatment. If you're extremely generous you could think that ALTER .. SET STORAGE would be reasonable to be run by the db-owner. However, that's not something you do on an ongoing basis -- you just do it once -- so it seems pointless. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix psql \?'s entries for \dp and \z.
- dda9f8e7bc2e 16.0 landed
-
psql: Add support for \dpS and \zS.
- d913928c9c5e 16.0 landed
-
Add grantable MAINTAIN privilege and pg_maintain role.
- 60684dd834a2 16.0 landed