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

Using ctid as IV base instead of offset calculation #107

Merged
merged 3 commits into from
Feb 7, 2024

Commits on Jan 25, 2024

  1. Using ctid as IV base instead of offset calculation

    This commit modifies the ID calculation of normal tuples to just
    use the alrady exisitng ItemPointer to offset the IV instead of
    the actual offset addresses, as the ItemPointer doesn't change during
    moves and also easier to use for replication.
    
    As part of this, the structure of the IV is also changed: instead of
    using the offset as the base number, and incrementing it sequentially,
    we now insert the "base" ItemPointer at the high part of the IV, and
    start the counter at the other end, at the low part of the IV.
    
    This means that we are no longer using AES-CTR, but instead rely on a
    custom AES based encryption, but this is also required for toast, as
    with that, we can't rely on the uniqueness of the address in the entire
    data range.
    
    Old encryption tests are also deleted, as they no longer work with
    these changes.
    dutow committed Jan 25, 2024
    Configuration menu
    Copy the full SHA
    2573a0b View commit details
    Browse the repository at this point in the history

Commits on Jan 30, 2024

  1. Fixing review comments

    dutow committed Jan 30, 2024
    Configuration menu
    Copy the full SHA
    15367e3 View commit details
    Browse the repository at this point in the history

Commits on Feb 5, 2024

  1. Configuration menu
    Copy the full SHA
    b34095e View commit details
    Browse the repository at this point in the history