Manufacturer / project: Greenmask project
When does it fit?
Consider it for a PostgreSQL dump-and-restore workflow where you can maintain transformation rules. Local tooling and inspectable configuration fit teams that already operate their database backups and restores. 1 · 2 · 3
Fit still depends on your mandatory requirements.
What should you check before choosing?
Verify sensitive columns, key consistency and uniqueness after restore. MySQL support is beta/in progress. Release 0.2.25 fixes COPY encoding corruption for certain transformed values; upgrading does not repair older affected dumps. Recreate them. 1 · 2 · 3 · 4
What must your PoC prove?
Restore a subset with cycles and test key mappings, NULLs and unique columns. Include backslashes, COPY control markers and control characters to verify the 0.2.25 fix. Keep salt handling and regenerated dumps in the run record.
Acceptance plan, not a product test result. Execution scope and limits.
Deployment and license
Local binary/CLI in a PostgreSQL logical-dump pipeline, using local or supported object storage. Verify PostgreSQL and restore-tool versions. Reviewed release: 0.2.25, 30 September 2026. 1 · 2 · 3 · 4
Apache-2.0 according to the repository. Storage services, databases and custom extensions have their own terms. 1 · 2 · 3 · 4
Confirm the entitled version and operating requirements.
How you work with it
Configure subsets and transformers in YAML, dump, restore and run business assertions. Configuration files are exportable; they depend on Greenmask transformer behavior and PostgreSQL, not a universal model format. 1 · 2 · 3 · 4
Export does not establish compatibility with another runtime.
Documented capabilities
Documentation is not a measured benchmark. Unclear is missing evidence; the comparison matrix explains the gap.
Sources and scope
Sources can cover different releases; they do not establish measured performance.
Open the cited sources (4)
- Greenmask repository
PostgreSQL logical dump/transform/restore pipeline; YAML configuration; Apache-2.0. MySQL remains beta/in progress.
Source checked: 2026-10-11 - Database subsetting
Schema-aware joins and recursive selection; complex queries can require indexes and tuning.
Source checked: 2026-10-11 - Transformation engines
Hash-based consistency depends on inputs and stable parameters/salt; default random generation is not repeated-run seed proof; uniqueness must be checked.
Source checked: 2026-10-11 - Greenmask 0.2.25, 30 September 2026
COPY encoder corruption fix for certain transformer outputs; older affected dumps must be regenerated.
Source checked: 2026-10-11