Horton
Menu

Re: sandboxing untrusted code

Jeff Davis <pgsql@j-davis.com>

View thread
From: Jeff Davis <pgsql@j-davis.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Noah Misch <noah@leadboat.com>, Jacob Champion <jacob.champion@enterprisedb.com>
Date: 2026-04-24T00:27:58Z
Lists: pgsql-hackers 
On Sat, 2026-04-18 at 15:11 -0400, Robert Haas wrote:
> Returning to this topic after some time, I have realized that both of
> these rules are inadequate.

I agree with others that perfection isn't required.

I am slightly worried about how hard this will be to document. But if
we solve a good portion of the problem, we can at least document some
best practices, even if the underlying mechanisms are complex.

Regards,
	Jeff Davis

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix possible crash in tablesync worker.

  2. Display 'password_required' option for \dRs+ command.

  3. Restart the apply worker if the 'password_required' option is changed.

  4. Fix possible logical replication crash.

  5. Add new predefined role pg_create_subscription.

  6. Expand AclMode to 64 bits

  7. More cleanup of a2ab9c06ea.

  8. Respect permissions within logical replication.

  9. Improve table locking behavior in the face of current DDL.