| From: | Kai Wagner <kai(dot)wagner(at)percona(dot)com> |
|---|---|
| To: | Johnathan Tiamoh <johnathantiamoh(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres database encryption |
| Date: | 2024-03-19 18:20:26 |
| Message-ID: | 3adaed22-5e25-4c12-964b-65e70b0c9217@percona.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hey,
On 19/03/2024 14:22, Johnathan Tiamoh wrote:
> Hello,
>
>
> Good morning. Please I wish to find out the best way of encrypting a
> Postgres database.
>
> This could either be encrypting a whole database ( I don’t if this is
> possible), a specific table and a specific tablespace.
There is no default incore mechanism to do that. Depending on your treat
vector, OS-Level could be fine or you need to go with any of the incore
rebuilds available by some vendors.
We're currently working on another mechanism, which enables you to
encrypt on a table level. Of course, completely open source project,
available on GitHub https://github.com/Percona-Lab/pg_tde
Would be happy, if you can give it a shot, and share your thoughts and
feedback.
>
>
> King regards
> Johnathan T.
--
Kai Wagner
Sr. Engineering Manager, Percona
e: kai(dot)wagner(at)percona(dot)com
w: www.percona.com
Databases Run Better with Percona.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-03-19 18:57:28 | Re: Postgres database encryption |
| Previous Message | Adrian Klaver | 2024-03-19 16:03:15 | Re: Query on Postgres SQL transaction |