Date: Tue, 3 Sep 2019 12:56:15 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Shawn Wang <shawn.wang@highgo.ca>
Cc: pgsql-hackers@lists.postgresql.org, Antonin Houska <ah@cybertec.at>,
	Ants Aasma <ants.aasma@eesti.ee>
Subject: Re: WIP: Data at rest encryption
Message-ID: <20190903165615.GA16727@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <156472805641.1401.3119816532289012709.pgcf@coridan.postgresql.org>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On 2019-Aug-02, Shawn Wang wrote:

> Hi Antonin,
> It is very glad to see the new patch. I used the public patches a long time ago.
> I did some tests like the stream replication, much data running, temporary files encryption.
> I found that there is an issue in the src/backend/storage/file/encryption.c. You should put block_size = EVP_CIPHER_CTX_block_size(ctx); under the #ifdef USE_ASSERT_CHECKING.
> There is some problem to merge your patches to the latest kernel in the pg_ctl.c.

Is a new, fixed version going to be posted soon?  It's been a while.

Also, apologies if this has been asked before, but: how does this patch
relate to the stuff being discussed in
https://postgr.es/m/031401d3f41d$5c70ed90$1552c8b0$@lab.ntt.co.jp ?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services