Skip to content

README.md

Latest commit

 

History

History
73 lines (53 loc) · 2 KB

README.md

File metadata and controls

73 lines (53 loc) · 2 KB
Raw

Building the PAC DuckDB Extension

Prerequisites

  • git (with submodule support)
  • cmake (>= 3.11)
  • ninja (optional but recommended — significantly faster builds)
  • C++ compiler with C++11 support (clang recommended, especially for benchmarks)

Clone

git clone --recurse-submodules https://github.com/cwida/privacy.git
cd privacy

If you already cloned without --recurse-submodules, run:

git submodule update --init --recursive

Build

GEN=ninja make        # release build (recommended)
make                  # release build without ninja
make debug            # debug build

The extension is built into build/release/extension/pac/pac.duckdb_extension.

Run Tests

# all tests
make test

# PAC SQL tests only
./build/release/test/unittest --test-dir . "test/sql/pac*"

# C++ unit tests
./build/release/extension/pac/pac_test_runner

Build Flags

Compile-time flags control algorithm variants, primarily for benchmarking and scientific reproducibility. Set them via cmake defines (e.g., -DPAC_NOBUFFERING=1).

Flag Effect
PAC_NOBUFFERING Disable input buffering (lazy allocation)
PAC_NOCASCADING Pre-allocate all accumulator levels
PAC_NOSIMD No-cascading with SIMD-unfriendly update kernels and auto-vectorization disabled
PAC_NOBOUNDOPT Disable bound optimization (only affects min/max)
PAC_SIGNEDSUM Disable handling negative values in signed sums using separate (negated) counters
PAC_EXACTSUM Disable approximate sum optimization, use exact cascading (implies signedsum)

Updating the DuckDB Version

The DuckDB version is pinned via the duckdb and extension-ci-tools submodules. To update to a new release:

cd duckdb && git fetch --tags && git checkout v1.X.0
cd ../extension-ci-tools && git fetch && git checkout origin/v1.X.0
cd ..
git add duckdb extension-ci-tools
git commit -m "Bump DuckDB to v1.X.0"

Replace v1.X.0 with the target version tag.