Updated release notes and docs with pg_tde_basic access method

modified:   documentation/docs/release-notes/release-notes.md
	modified:   documentation/docs/test.md
	modified:   documentation/mkdocs.yml
pull/209/head
Anastasia Alexadrova 1 year ago
parent b5ef82966b
commit 4c8fe18cb7
  1. 4
      documentation/docs/release-notes/release-notes.md
  2. 8
      documentation/docs/test.md
  3. 2
      documentation/mkdocs.yml

@ -6,11 +6,13 @@
## Beta (2024-06-30) ## Beta (2024-06-30)
With this version, the access method for `pg_tde` extension is renamed `pg_tde_basic`. Use this access method name to create tables. Find guidelines in [Test TDE](../test.md) tutorial.
The Beta version introduces the following bug fixes and improvements: The Beta version introduces the following bug fixes and improvements:
* Fixed the issue with `pg_tde` running out of memory used for decrypted tuples. The fix introduces the new component `TDEBufferHeapTupleTableSlot` that keeps track of the allocated memory for decrypted tuples and frees this memory when the tuple slot is no longer needed. * Fixed the issue with `pg_tde` running out of memory used for decrypted tuples. The fix introduces the new component `TDEBufferHeapTupleTableSlot` that keeps track of the allocated memory for decrypted tuples and frees this memory when the tuple slot is no longer needed.
* Fixed the issue with adjusting a current position in a file by using raw file descriptor for the lseek function. (Thanks to user _rainhard_ for providing the fix) * Fixed the issue with adjusting a current position in a file by using raw file descriptor for the `lseek` function. (Thanks to user _rainhard_ for providing the fix)
* Enhanced the init script to consider a custom superuser for the POSTGRES_USER parameter when `pg_tde` is running via Docker (Thanks to _Alejandro Paredero_ for reporting the issue) * Enhanced the init script to consider a custom superuser for the POSTGRES_USER parameter when `pg_tde` is running via Docker (Thanks to _Alejandro Paredero_ for reporting the issue)

@ -2,18 +2,18 @@
To check if the data is encrypted, do the following: To check if the data is encrypted, do the following:
1. Create a table in the database for which you have [enabled `pg_tde`](setup.md). Enabling `pg_tde` extension creates the table access method `pg_tde`. To enable data encryption, create the table using this access method as follows: 1. Create a table in the database for which you have [enabled `pg_tde`](setup.md). Enabling `pg_tde` extension creates the table access method `pg_tde_basic`. To enable data encryption, create the table using this access method as follows:
```sql ```sql
CREATE TABLE <table_name> (<field> <datatype>) USING pg_tde; CREATE TABLE <table_name> (<field> <datatype>) USING pg_tde_basic;
``` ```
!!! hint !!! hint
You can enable data encryption by default by setting the `default_table_access_method` to `pg_tde`: You can enable data encryption by default by setting the `default_table_access_method` to `pg_tde_basic`:
```sql ```sql
SET default_table_access_method = pg_tde; SET default_table_access_method = pg_tde_basic;
``` ```
2. Run the following function: 2. Run the following function:

@ -166,7 +166,7 @@ nav:
- How to: - How to:
- Use reference to external parameters: external-parameters.md - Use reference to external parameters: external-parameters.md
- Release notes: - Release notes:
- "pg_tde tech preview": release-notes/release-notes.md - "pg_tde release notes": release-notes/release-notes.md
- uninstall.md - uninstall.md
- contribute.md - contribute.md

Loading…
Cancel
Save