| From: | John Morris <john(dot)morris(at)crunchydata(dot)com> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Temporary file access API |
| Date: | 2022-09-27 16:22:39 |
| Message-ID: | BYAPR13MB2677AD2D389ABE0014BD5CBBA0519@BYAPR13MB2677.namprd13.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* So I think that code simplification and easy adoption of in-memory data
changes (such as encryption or compression) are two rather distinct goals.
admit that I'm running out of ideas how to develop a framework that'd be
useful for both.
I’m also wondering about code simplification vs a more general encryption/compression framework. I started with the current proposal, and I’m also looking at David Steele’s approach to encryption/compression in pgbackrest. I’m beginning to think we should do a high-level design which includes encryption/compression, and then implement it as a “simplification” without actually doing the transformations.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashwin Agrawal | 2022-09-27 16:31:24 | Re: Backends stalled in 'startup' state |
| Previous Message | Tom Lane | 2022-09-27 16:21:01 | Re: GUC tables - use designated initializers |