Re: RFC: Additional Directory for Extensions
David E. Wheeler <david@justatheory.com>
From: "David E. Wheeler" <david@justatheory.com>
To: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Cc: Matheus Alcantara <matheusssilv97@gmail.com>,
Andrew Dunstan <andrew@dunslane.net>,
Peter Eisentraut <peter@eisentraut.org>,
Craig Ringer <craig.ringer@enterprisedb.com>,
Robert Haas <robertmhaas@gmail.com>,
Alvaro Herrera <alvherre@alvh.no-ip.org>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2025-03-03T15:10:44Z
Lists: pgsql-hackers
On Mar 3, 2025, at 10:05, David E. Wheeler <david@justatheory.com> wrote: > Very nice writeup, thank you. Makes me wish for the bandwidth to get back to and start refining the PGXN OCI RFC Forgot to link to the POC[1]. The RFC[2] is not OCI-specific, but the POC demonstrates the “full content” version. Will likely want to modify the binary distribution RFC to adopt a standard layout that allows for volume mounting to “install” an extension. Best, David 1: https://justatheory.com/2024/06/trunk-oci-poc/ 2: https://github.com/pgxn/rfcs/pull/2
Commits
-
doc: Flesh out extension docs for the "prefix" make variable
- 0064020680c1 18.0 landed
-
Fix extension control path tests
- b7076c1e7f43 18.0 landed
-
extension_control_path
- 4f7f7b037585 18.0 landed