From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Transparent column encryption |
Date: | 2023-03-10 07:18:34 |
Message-ID: | 7a430d89-233b-5cd7-6892-9fed06695d39@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Here is an updated patch. I have done some cosmetic polishing and fixed
a minor Windows-related bug.
In my mind, the patch is complete.
If someone wants to do some in-depth code review, I suggest focusing on
the following files:
* src/backend/access/common/printtup.c
* src/backend/commands/colenccmds.c
* src/backend/commands/tablecmds.c
* src/backend/parser/parse_param.c
* src/interfaces/libpq/fe-exec.c
* src/interfaces/libpq/fe-protocol3.c
* src/interfaces/libpq/libpq-fe.h
(Most other files are DDL boilerplate or otherwise not too interesting.)
Attachment | Content-Type | Size |
---|---|---|
v18-0001-Automatic-client-side-column-level-encryption.patch | text/plain | 462.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2023-03-10 08:04:15 | Re: Combine pg_walinspect till_end_of_wal functions with others |
Previous Message | Michael Paquier | 2023-03-10 06:59:04 | Requiring recovery.signal or standby.signal when recovering with a backup_label |