Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PG-1437 Do not duplicate frontend sources in meson.build #182

Open
wants to merge 2 commits into
base: TDE_REL_17_STABLE
Choose a base branch
from

Conversation

jeltz
Copy link
Collaborator

@jeltz jeltz commented Apr 1, 2025

There is no reason why we cannot just concatenate the two lists. And while at it we also sort and reindent the lists.

There is no reason why we cannot just concatenate the two lists. And while
at it we also sort and reindent the lists.
@jeltz jeltz requested review from dutow and dAdAbird as code owners April 1, 2025 22:16
Copy link

@AndersAstrand AndersAstrand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might have missed some previous discussion, but are we sure that adding an assumption that the frontend code is a subset of the extension code is what we want to do?

I'm thinking it might compound the possible confusion by #ifdef FRONTEND sprinkled throughout the code rather than help.

The old naming leads me to believe the list of files for "decrypt" arent necessarily frontend files but files used by both the extension and the frontend?

So I'd suggest either separate lists of files for frontend and extension, or if we want to group the files needed for decryption separately have both the frontend and extension file list concatenate it.

@@ -74,35 +71,35 @@ install_data(
# toast_descrypt needs to be the first test when running with pg_tde

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we're cleaning up this file this typo should probably be fixed while at it

@jeltz
Copy link
Collaborator Author

jeltz commented Apr 4, 2025

Good point, need to think about it. But calling them decrypt isn't entirely accurate either because those files are for the following:

  • Reading and writing to the keyring file
  • Reading the key file (require connecting to key server)
  • Reading encrypted WAL (requires connecting to key server)

But it does not include for example:

  • Reading encrypted relations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants