open-dsi
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
60701 Commits
38 Branches
662 Tags
731 MiB
 
 
 
 
 
 
Tag: Branch: Tree: d0b53f35fb
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd0b53f35fb'
${ noResults }
postgres/contrib/pg_tde/documentation/docs/release-notes/release-notes-v1.0.md

5.1 KiB
Raw Blame History

pg_tde 1.0 ({{date.GA10}})

The pg_tde by Percona extension brings in Transparent Data Encryption (TDE) :octicons-link-external-16: to PostgreSQL and enables you to keep sensitive data safe and secure.

Get Started{.md-button}

Release Highlights

  • pg_tde 1.0 is now GA (Generally Available)

And stable for encrypting relational data in PostgreSQL using Transparent Data Encryption (TDE) :octicons-link-external-16:. This milestone brings production-level data protection to PostgreSQL workloads.

  • WAL encryption is still in Beta

The WAL encryption feature is currently still in beta and is not effective unless explicitly enabled. It is not yet production ready. Do not enable this feature in production environments.

Upgrade considerations

pg_tde 1.0 is not backward compatible with previous pg_tde versions, like Release Candidate 2, due to significant changes in code. This means you cannot directly upgrade from one version to another. You must do a clean installation of pg_tde.

Known issues

  • The default mlock limit on Rocky Linux 8 for ARM64-based architectures equals the memory page size and is 64 Kb. This results in the child process with pg_tde failing to allocate another memory page because the max memory limit is reached by the parent process.

To prevent this, you can change the mlock limit to be at least twice bigger than the memory page size:

  • temporarily for the current session using the ulimit -l <value> command.
  • set a new hard limit in the /etc/security/limits.conf file. To do so, you require the superuser privileges.

Adjust the limits with caution since it affects other processes running in your system.

Changelog

New Features

Improvements

Bugs Fixed