| From: | Alastair Turner <minion(at)decodable(dot)me> |
|---|---|
| To: | Hosney Osman <hosneybinosman(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for Integrating Data Masking and anonymization into PostgreSQL |
| Date: | 2024-10-23 13:25:06 |
| Message-ID: | CAC0Gmyyd-BtNFFxQUpM158doAt4-YHLJ=MvMvoteniLS6tQNJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Hosney
On Wed, 23 Oct 2024, 15:17 Hosney Osman, <hosneybinosman(at)gmail(dot)com> wrote:
> Dear PostgreSQL Development Team,
>
> I am writing to propose the development of native data masking and
> anonymization features within PostgreSQL. As a long-time user of
> PostgreSQL,
>
> I have observed a growing need for efficient and secure data handling,
> particularly in compliance with regulations like GDPR
>
This requirement already seems to be well served by extensions.
pg_anonymize, for instance, uses the meta data tools available in the
database, like security labels, to manage the values returned to users.
Is there any functionality, or usability, in this area which you believe
can't be delivered by an extension?
Regards
Alastair
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey M. Borodin | 2024-10-23 13:32:21 | Re: Using read_stream in index vacuum |
| Previous Message | Erik Sjoblom | 2024-10-23 13:18:52 | Re: Unexpected table size usage for small composite arrays |