| From: | Kai Wagner <kai(dot)wagner(at)percona(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Chris Travers <chris(dot)travers(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, "Clay Jackson (cjackson)" <Clay(dot)Jackson(at)quest(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Subject: | Re: Enquiry about TDE with PgSQL |
| Date: | 2025-11-02 10:14:58 |
| Message-ID: | CAG0qCNgV+Ra72vTvCoTZqn7KUUsXvp3N=ZUgACgMTDDPt8WTkA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Nov 1, 2025 at 2:58 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> If you want to move forward with TDE without waiting to see if the
> temporary file compression patch will reduce the TDE code impact, you
> need to dig into how the community does feature calculus and how that
> calculus can be changed --- this is not something technology can fix.
>
I fully agree here, and as I stated above, I don't question this at all, as
this is the strength of the diverse and spread community. Looking at this
thread alone, and the multiple different "users" popping up, that see the
need and would like to see TDE in core or in an extension drives my
thinking as it makes sense to start thinking and looking into the temp file
compression already right now, if and how this could make our code changes
easier, or if additional extensibility should be directly part of the first
patch, so you can enable it through its extension. Either way, it should be
considered and kept in mind now, not after the fact, or we will continue to
spin this wheel. And this thinking and willingness alone, to actually be
open to that idea, requires some upfront discussion, so you at least know
you are welcome to work on it without wasting effort, because no one will
ever want to merge. (and yes, of course everyone can work on whatever they
want at any point in time, but people might prefer working on something
that actually benefits the project and is welcome, rather than ending in
>/dev/null)
Given your experience Bruce, can you offer us some advice on how you would
approach it currently? What do you think makes the most sense, and how
should we proceed with collaboration to at least see a small change in
making this happen in the future?
>
> Companies are willing to add the code weight because it is a sale for
> them, and customers are willing to pay to meet the check box --- that
> calculus just doesn't work in the community.
>
And this should always be at the forefront, as this makes the project
exactly as strong as it is today.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us>
> https://url.avanan.click/v2/r01/___https://momjian.us___.YXAzOnBlcmNvbmE6YTpnOmZhM2VjN2JlNjcyOTZmMGQwMjEzOGM1NWU5OTA5NzM0Ojc6ZDgxOTo3NzQ0MzQwZjhmODA4YmY1ZjFiZmFlMzdlNmE4MzUxYzc0NGU0NTIwMjA5YWU1Mjk2NjQ5YjFiZjk0NDI3MDNjOnA6VDpO
> EDB
> https://url.avanan.click/v2/r01/___https://enterprisedb.com___.YXAzOnBlcmNvbmE6YTpnOmZhM2VjN2JlNjcyOTZmMGQwMjEzOGM1NWU5OTA5NzM0Ojc6MjZhZTplMDhhZWQ5Nzg3YmVjODI4MDQ5YmU2ODc1MGExMTVmMmRmOTVlOTk2N2FmM2Y1N2VkN2VmYTZhYWMyZDQ1MzE3OnA6VDpO
>
> Do not let urgent matters crowd out time for investment in the future.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-11-02 15:21:05 | Re: [ANNOUNCE] BISCUIT – A Bitmap-Based Indexed Search Extension for PostgreSQL |
| Previous Message | Michał Kłeczek | 2025-11-02 07:53:22 | Re: [ANNOUNCE] BISCUIT – A Bitmap-Based Indexed Search Extension for PostgreSQL |