From: | Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: encrypting data stored in PostgreSQL |
Date: | 2014-04-09 21:16:34 |
Message-ID: | CAD3a31VHdLG7t+EwkDOQZ8kC8nGDNiWRkj-czi515qShBSVzHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> On 04/09/2014 02:52 PM, John R Pierce wrote:
>
> On 4/9/2014 1:40 PM, CS_DBA wrote:
>
> Hi All;
>
> We have a client with this requirement:
>
> At rest data must be encrypted with a unique client key
>
> Any thoughts on how to pull this off for PostgreSQL stored data?
>
> I looked at this a while ago because I have clients who might require this
in the future. ISTM you should be able to have your PG data directory
stored on an encrypted filesystem. I believe this will decrease
performance, but I have no idea by how much.
Does anyone else have experience with such a setup, or knowledge of how bad
the performance hit might be? Or other factors to take into consideration?
Thanks.
Ken
--
AGENCY Software
A Free Software data system
By and for non-profits
*http://agency-software.org/ <http://agency-software.org/>*
*https://agency-software.org/demo/client
<https://agency-software.org/demo/client>*
ken(dot)tanzer(at)agency-software(dot)org
(253) 245-3801
Subscribe to the mailing
list<agency-general-request(at)lists(dot)sourceforge(dot)net?body=subscribe>
to
learn more about AGENCY or
follow the discussion.
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2014-04-09 21:28:08 | Re: encrypting data stored in PostgreSQL |
Previous Message | Rob Sargent | 2014-04-09 21:07:00 | Re: encrypting data stored in PostgreSQL |