Feedback-ID: i76984098:Fastmail
Message-ID: <0c030801-1594-4b60-91e1-f84e175a80f8@aklaver.com>
Date: Sat, 1 Nov 2025 14:15:43 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Enquiry about TDE with PgSQL
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>, Kai Wagner <kai.wagner@percona.com>,
 Chris Travers <chris.travers@gmail.com>, Christophe Pettus
 <xof@thebuild.com>, "Clay Jackson (cjackson)" <Clay.Jackson@quest.com>,
 pgsql-general <pgsql-general@postgresql.org>,
 Laurenz Albe <laurenz.albe@cybertec.at>,
 Ron Johnson <ronljohnsonjr@gmail.com>
References: <a1dae4a583d560a90c67872b766ead02ddb13e51.camel@cybertec.at>
 <aQPDvqUzZVKkaxsS@momjian.us>
 <CAG0qCNhL=SEB4vc4v48PxN1F-t8htC463TpX7KDNWQ-s3s8dtA@mail.gmail.com>
 <aQTNmM-3VeTRZdx0@momjian.us>
 <FC8C7F2D-CD38-42C7-80D3-516239B70A2D@thebuild.com>
 <aQVScCjItvCtgVPn@momjian.us>
 <CO1PR19MB4984B665A5F9F38A5E0FB5969BF9A@CO1PR19MB4984.namprd19.prod.outlook.com>
 <3DC589BC-A5F6-49BC-BFFC-F1FCB0FF7E95@thebuild.com>
 <CAKt_ZfuwPgG_nJHp6S=8k_+NdA6Op7hE0z7+s4-HuBqr1cnwsg@mail.gmail.com>
 <CAG0qCNjd2m9Ej1ZEwuCCkgsqJz0vnso3ZFwjKCxzwUfnfu=SNw@mail.gmail.com>
 <aQYSAGEfd116_58N@momjian.us>
 <3985797c-639f-4825-9fa9-98a48b37f380@aklaver.com>
 <CAKAnmmJ4yRTb-TV=ik0aoEZsWzDzuKRgCjXFfF5DCzR5jiCQdA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAKAnmmJ4yRTb-TV=ik0aoEZsWzDzuKRgCjXFfF5DCzR5jiCQdA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/0c030801-1594-4b60-91e1-f84e175a80f8%40aklaver.com>
Precedence: bulk

On 11/1/25 11:34, Greg Sabino Mullane wrote:
> On Sat, Nov 1, 2025 at 11:32 AM Adrian Klaver <adrian.klaver@aklaver.com 
> <mailto:adrian.klaver@aklaver.com>> wrote:
> 
>     The community does provide it, just not the version of Postgres
>     released here:
> 
> 
> I'm not sure of your point here. Companies have forked versions / 
> patches, yes, but not sure how that equates to "community-provided"

Well this gets in to a pet peeve of my with regard to OSS and the 
definition of 'community', it seems to adjust in size of coverage 
depending on the argument.

For a recent thread on -www that gets into this, as concerns 
contributors, see:

https://www.postgresql.org/message-id/aJ9ur1eSnk5pp9aD%40msg.df7cb.de

To get to said contributors list you go:

https://www.postgresql.org/community/contributors/

where you see folks recognized for their work outside the core code.

Examples of the expanded 'commmunity':

1) From the 'community' site you can go to:

https://www.postgresql.org/download/

where that packaging is done outside of core.

2) Again from postgresql.org:

https://www.postgresql.org/docs/18/external-extensions.html

"PostgreSQL is designed to be easily extensible. For this reason, 
extensions loaded into the database can function just like features that 
are built in. The contrib/ directory shipped with the source code 
contains several extensions, which are described in Appendix F. Other 
extensions are developed independently, like PostGIS. Even PostgreSQL 
replication solutions can be developed externally. For example, Slony-I 
is a popular primary/standby replication solution that is developed 
independently from the core project."

3) Of course there is:

https://www.postgresql.org/community/

"PostgreSQL is well-supported by its active community."


To me that means extensions provided by members of the 'community' are 
'community-provided'?


> 
> Cheers,
> Greg
> 
> --
> Crunchy Data - https://www.crunchydata.com <https://www.crunchydata.com>
> Enterprise Postgres Software Products & Tech Support
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com