From: | Hosney Osman <hosneybinosman(at)gmail(dot)com> |
---|---|
To: | Alastair Turner <minion(at)decodable(dot)me> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal for Integrating Data Masking and anonymization into PostgreSQL |
Date: | 2024-10-27 23:00:22 |
Message-ID: | CA++4CRkZegXsfPiH8WKs1+caXV_PS2dkhZd+vy3rhkrcQ7PTUQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
could you please provide me with reference or article or example for this
scenario
for example i have schema include 4 table
and i want to anonymize it in another schema
how to do that
On Wed, Oct 23, 2024 at 4:25 PM Alastair Turner <minion(at)decodable(dot)me> wrote:
> 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 | Michael Paquier | 2024-10-28 00:07:50 | Re: Set query_id for query contained in utility statement |
Previous Message | Noah Misch | 2024-10-27 21:45:11 | Re: race condition in pg_class |