Stephen Frost <sfrost@snowman.net> wrote:
> Perhaps this is all too meta and we need to work through some specific
> ideas around just what this would look like. In particular, thinking
> about what this API would look like and how it would be used by
> reorderbuffer.c, which builds up changes in memory and then does a bare
> write() call, seems like a main use-case to consider. The gist there
> being "can we come up with an API to do all these things that doesn't
> require entirely rewriting ReorderBufferSerializeChange()?"
>
> Seems like it'd be easier to achieve that by having something that looks
> very close to how write() looks, but just happens to have the option to
> run the data through a stream cipher and maybe does better error
> handling for us. Making that layer also do block-based access to the
> files underneath seems like a much larger effort that, sure, may make
> some things better too but if we could do that with the same API then it
> could also be done later if someone's interested in that.
My initial proposal is in this new thread:
https://www.postgresql.org/message-id/4987.1644323098%40antos
--
Antonin Houska
Web: https://www.cybertec-postgresql.com