On Thu, 2023-01-19 at 10:45 -0500, Robert Haas wrote: > I wouldn't be OK with writing our own connection string parser for > this purpose, but using PQconninfoParse seems OK. We still have to > embed knowledge of which connection string parameters can trigger > local file access, but that doesn't seem like a massive problem to > me.
Another idea (I discussed with Andres some time ago) was to have an option to libpq to turn off file access entirely. That could be a new API function or a new connection option. That would be pretty valuable by itself. Though we might want to support a way to pass SSL keys as values rather than file paths, so that we can still do SSL. So perhaps the answer is that it will be a small patch to get non- superuser subscription owners, but we need three or four preliminary patches first. -- Jeff Davis PostgreSQL Contributor Team - AWS