Re: [PATCH] Support reading large objects with pg_read_all_data
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Nitin Motiani <nitinmotiani@google.com>
Cc: Dilip Kumar <dilipbalaut@gmail.com>, pgsql-hackers@postgresql.org
Date: 2026-02-23T17:07:21Z
Lists: pgsql-hackers
Attachments
On Fri, Feb 13, 2026 at 11:17:28AM -0600, Nathan Bossart wrote: > This looks pretty good to me. I'd like to let it sit on the lists a little > while longer in case anyone else has feedback or objections. Assuming > those don't materialize in the next week or so, I will proceed with > committing it. Here's what I have staged for commit. I didn't understand the reasoning behind not giving pg_write_all_data privileges on large objects. Your commit message mentions that "granting write access would imply write permissions on a system catalog" (which I assume is referring to pg_largeobject), but if granting UPDATE on a large object is sufficient to allow updating portions of that catalog, then I see no reason to be so strict with pg_write_all_data. It still doesn't allow updating the catalog directly. -- nathan
Commits
-
Allow pg_{read,write}_all_data to access large objects.
- d98197602790 19 (unreleased) landed