Re: Key encryption and relational integrity - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Key encryption and relational integrity
Date
Msg-id a7a9ea11-4824-fd2f-357c-bdd6c29a93ad@aklaver.com
Whole thread Raw
In response to Re: Key encryption and relational integrity  (Moreno Andreo <moreno.andreo@evolu-s.it>)
Responses Re: Key encryption and relational integrity  (Moreno Andreo <moreno.andreo@evolu-s.it>)
List pgsql-general
On 3/29/19 9:01 AM, Moreno Andreo wrote:

> And I tried to find a solution, and since I did not like that much what 
> I found (and it seems that neither you do :-) ), I came here hoping that 
> someone would share his experience to shed some light on the topic.

 From what you have posted the biggest issue you are having is less then 
real time search on patient names due to the need to meet 
pseudonymisation. To me that is always going to be a problem as there 
are two opposing forces at work, overhead to implement pseudonymisation 
vs quick lookup. Might be time to lower expectations on what can be done.

> 
> 
>>          hp
>>
> 
> 
> 
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Issue with COMMITs stuck on "AccessExclusiveLock on object 0 of class1262 of database 0"
Next
From: "Peter J. Holzer"
Date:
Subject: Re: Key encryption and relational integrity