Hi,
Thank you, Oleg Tselebrovskiy, for your valuable review, here are the fixes
Best regards,
Viktoria Shepard
ср, 12 окт. 2022 г. в 12:19, Виктория Шепард :
> Hi,
>
> Here is an idea of how to read masking options from a file. Please, take a
> look.
>
> пн, 10 окт. 2022 г. в 14:54, Олег Целебр
Hi,
Here is an idea of how to read masking options from a file. Please, take a
look.
пн, 10 окт. 2022 г. в 14:54, Олег Целебровский :
> Hi,
>
> I applied most of suggestions: used separate files for most of added code,
> fixed typos/mistakes, got rid of that pesky TODO that was already
> impleme
Hi,
I applied most of suggestions: used separate files for most of added code,
fixed typos/mistakes, got rid of that pesky TODO that was already implemented,
just not deleted.
Added tests (and functionality) for cases when you need to mask columns in
tables with the same name in different sch
Hi,
I took a look, here are several suggestions for improvement:
- Masking is not a main functionality of pg_dump and it is better to write
most of the connected things in a separate file like parallel.c or
dumputils.c. This will help slow down the growth of an already huge pg_dump
file.
- Also i
Hi,
On Mon, Oct 03, 2022 at 06:30:17PM +0300, Олег Целебровский wrote:
>
> Hello, here's my take on masking data when using pg_dump
>
> The main idea is using PostgreSQL functions to replace data during a SELECT.
> When table data is dumped SELECT a,b,c,d ... from ... query is generated, the
>
Hello, here's my take on masking data when using pg_dump
The main idea is using PostgreSQL functions to replace data during a SELECT.
When table data is dumped SELECT a,b,c,d ... from ... query is generated, the
columns that are marked for masking are replaced with result of functions on
those
