Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qY7gQ-000qN6-BU for pgsql-general@arkaria.postgresql.org; Mon, 21 Aug 2023 16:23:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qY7gO-008Mgc-VK for pgsql-general@arkaria.postgresql.org; Mon, 21 Aug 2023 16:23:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qY7gO-008MgJ-J0 for pgsql-general@lists.postgresql.org; Mon, 21 Aug 2023 16:23:12 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qY7gL-000CXF-0g for pgsql-general@lists.postgresql.org; Mon, 21 Aug 2023 16:23:11 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 013235C26EE; Mon, 21 Aug 2023 12:23:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 21 Aug 2023 12:23:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1692634987; x=1692721387; bh=Hn7qZAmLymRdAy104I3Nzg+pZm5M6oSBf5D hqdbgzpo=; b=ErSrZ6oC0uS7erFueG37LG5q5Yfjuimdxnyk5s5nFbGm9qAz2Y8 gjP+UMfCw5T4su9tMWXKh78rx1wbcxEuarTCyTYstMTaq53LesosbfVasn+cdRma UObTuJ5VA6ovViSPyngbM06hwgeCTHpq6/l+gSRqQdOUWv0EB2xIkCeIkfGdG8+K 3a0Q6zdPP83fa7rdT+hGN/SflkXaCAs8gIC08y2gTzbCFho7GLgzgBC+qGMTzfcB 8FhfT0IS/7nl/7xYnAs50B71FJZJbYEVA9EyvJtQBrxtlXdpGuWEIBmsHJt4ZmAY iYhrw5+VC5470A4BiAwdzKNlOv3td+pGPzg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1692634987; x= 1692721387; bh=Hn7qZAmLymRdAy104I3Nzg+pZm5M6oSBf5Dhqdbgzpo=; b=y Z8El+4WnAcJ1RX89wgkp/GxAuB8pTQuj/djsJCIwW8PbLKptfRbCJ6tSzNaoIwI/ y/DZNT8vZKtsTGX9LdhOIuZClXEKk2cL+A/OVBuR+W6XLJP6OlSm/XO1jQto3ExT nJkAc8mC+suF93YPCyU0MwfTWwN6kyhxVqoRGkR7fIqKp3/fn5cQZprXntCTNP+i bjYtH/LkiGd2VPFTWCLGaRmhBydyrIda8RHVNcaDRaq6wusfbI8XaVX4wPqShL4j wElNMEer5XECDWEqaOXIRGdj9r0GRSG+fg+pMBFXSXtoWDWMmMMjFmQk9HHiKLpu HasZ5mWPmWD/DkbBHx1JA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudduledguddttdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepleekgeejhfekteehfeduveetheeivdduheekudel teefvdffueehtddvgedtfeefnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughr ihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 21 Aug 2023 12:23:07 -0400 (EDT) Message-ID: <3b6f1910-e01c-44a1-c1ad-ccf0c1e98014@aklaver.com> Date: Mon, 21 Aug 2023 09:23:06 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0 Subject: Re: Will PostgreSQL 16 supports native transparent data encryption ? Content-Language: en-US To: Mostafa Fathy , pgsql-general@lists.postgresql.org References: From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/21/23 09:02, Mostafa Fathy wrote: > Hi there, > > It is mentioned here > https://www.postgresql.org/about/press/faq/#:~:text=Q%3A%20What%20features%20will%20PostgreSQL%2016%20have%3F  that native transparent data encryption is being worked on and it may be delivered with PostgreSQL 16. > > Is PostgreSQL 16 beta version includes native transparent data > encryption or not ? because I checked the docs > https://www.postgresql.org/docs/16/index.html >   and couldn't find > anything related to transparent data encryption. > > If not supported yet in the beta version I would like to know if > PostgreSQL 16 final version will support native transparent data > encryption or not? I can't find anything that says it is included and if it is not at this point(Beta) it will not be in the production release. -- Adrian Klaver adrian.klaver@aklaver.com