From 4c8fe18cb7d9de26f60cb7789ff605c9971e3481 Mon Sep 17 00:00:00 2001 From: Anastasia Alexadrova Date: Tue, 16 Jul 2024 11:44:35 +0300 Subject: [PATCH] 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 --- documentation/docs/release-notes/release-notes.md | 4 +++- documentation/docs/test.md | 8 ++++---- documentation/mkdocs.yml | 2 +- 3 files changed, 8 insertions(+), 6 deletions(-) diff --git a/documentation/docs/release-notes/release-notes.md b/documentation/docs/release-notes/release-notes.md index 87c4375a549..169eb41e61d 100644 --- a/documentation/docs/release-notes/release-notes.md +++ b/documentation/docs/release-notes/release-notes.md @@ -6,11 +6,13 @@ ## 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: * 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) diff --git a/documentation/docs/test.md b/documentation/docs/test.md index 81f2bdbe4ef..917fa3ee9a4 100644 --- a/documentation/docs/test.md +++ b/documentation/docs/test.md @@ -2,18 +2,18 @@ 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 - CREATE TABLE ( ) USING pg_tde; + CREATE TABLE ( ) USING pg_tde_basic; ``` !!! 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 - SET default_table_access_method = pg_tde; + SET default_table_access_method = pg_tde_basic; ``` 2. Run the following function: diff --git a/documentation/mkdocs.yml b/documentation/mkdocs.yml index 689bc1b23f2..1e496f93ea2 100644 --- a/documentation/mkdocs.yml +++ b/documentation/mkdocs.yml @@ -166,7 +166,7 @@ nav: - How to: - Use reference to external parameters: external-parameters.md - Release notes: - - "pg_tde tech preview": release-notes/release-notes.md + - "pg_tde release notes": release-notes/release-notes.md - uninstall.md - contribute.md