Re: Extend ALTER DEFAULT PRIVILEGES for large objects
Yugo Nagata <nagata@sraoss.co.jp>
From: Yugo Nagata <nagata@sraoss.co.jp>
To: Yugo NAGATA <nagata@sraoss.co.jp>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
pgsql-hackers@postgresql.org
Date: 2024-09-13T07:18:01Z
Lists: pgsql-hackers
Attachments
On Fri, 26 Apr 2024 17:54:06 +0900 Yugo NAGATA <nagata@sraoss.co.jp> wrote: > On Wed, 24 Apr 2024 16:08:39 -0500 > Nathan Bossart <nathandbossart@gmail.com> wrote: > > > On Tue, Apr 23, 2024 at 11:47:38PM -0400, Tom Lane wrote: > > > On the whole I find this proposed feature pretty unexciting > > > and dubiously worthy of the implementation/maintenance effort. > > > > I don't have any particularly strong feelings on $SUBJECT, but I'll admit > > I'd be much more interested in resolving any remaining reasons folks are > > using large objects over TOAST. I see a couple of reasons listed in the > > docs [0] that might be worth examining. > > > > [0] https://www.postgresql.org/docs/devel/lo-intro.html > > If we could replace large objects with BYTEA in any use cases, large objects > would be completely obsolete. However, currently some users use large objects > in fact, so improvement in this feature seems beneficial for them. I've attached a updated patch. The test is rewritten using has_largeobject_privilege() function instead of calling loread & lowrite, which makes the test a bit simpler. Thare are no other changes. Regards, Yugo Nagata -- Yugo Nagata <nagata@sraoss.co.jp>
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
psql: Fix tab-completion after GRANT/REVOKE on LARGE OBJECT and FOREIGN SERVER.
- ff0bcb248e6e 19 (unreleased) landed
-
psql: Improve psql tab completion for GRANT/REVOKE on large objects.
- 86c539c5af14 19 (unreleased) landed
-
Extend ALTER DEFAULT PRIVILEGES to define default privileges for large objects.
- 0d6c4776647f 18.0 landed
-
Convert tab-complete's long else-if chain to a switch statement.
- f391d9dc93a2 18.0 cited