From: Antonin Houska <ah@cybertec.at>
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Temporary file access API
Date: Tue, 08 Mar 2022 12:14:59 +0100
Message-ID: <27013.1646738099@antos> (raw)
In-Reply-To: <20220301143431.GT10577@tamriel.snowman.net>
References: <4987.1644323098@antos>
<20220301143431.GT10577@tamriel.snowman.net>
Stephen Frost <sfrost@snowman.net> wrote:
> * Antonin Houska (ah@cybertec.at) wrote:
> > Here I'm starting a new thread to discuss a topic that's related to the
> > Transparent Data Encryption (TDE), but could be useful even without that. The
> > problem has been addressed somehow in the Cybertec TDE fork, and I can post
> > the code here if it helps. However, after reading [1] (and the posts
> > upthread), I've got another idea, so let's try to discuss it first.
>
> Yeah, I tend to agree that it makes sense to discuss the general idea of
> doing buffered I/O for the temporary files that are being created today
> with things like fwrite and have that be independent of encryption. As
> mentioned on that thread, doing our own buffering and having file
> accesses done the same way throughout the system is just generally a
> good thing and focusing on that will certainly help with any TDE effort
> that may or may not happen later.
Thanks for your comments, the initial version is attached here.
The buffer size is not configurable yet. Besides the new API itself, the patch
series shows how it can be used to store logical replication data changes as
well as statistics. Further comments are welcome, thanks in advance.
--
Antonin Houska
Web: https://www.cybertec-postgresql.comAttachments:
temp_file_api_v1.tgz (application/gzip, 17.3K) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ah@cybertec.at, sfrost@snowman.net, pgsql-hackers@lists.postgresql.org
Subject: Re: Temporary file access API
In-Reply-To: <27013.1646738099@antos>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox