Displays the ParadeDB extension’s OSS license text directly from your PostgreSQL session.
Confirming an extension’s license lets legal and engineering teams validate compliance before shipping code to production or redistributing software.
Run SELECT * FROM pg_extension;
. Verify paradedb
appears with its version so you know the path PostgreSQL used during CREATE EXTENSION.
PostgreSQL stores extension scripts under $SHAREDIR/extension
. Query pg_extension
and concatenate the directory to build the full path, then call pg_read_file()
to stream the text.
1. Identify the share path: SHOW shared_preload_libraries;
2. Read the license: SELECT pg_read_file(pg_extension_config_dump_filename(e.oid)::text || '/../../../LICENSE') AS license_text FROM pg_extension e WHERE e.extname = 'paradedb';
Yes. In psql
type \!
to execute shell commands, then cat $(pg_config --sharedir)/extension/paradedb--*.sql | grep -A5 'LICENSE'
.
Check the license type (e.g., Apache-2.0), notice any “Commons Clause” or usage restrictions, and record the commit SHA for auditing.
Automate checks in CI using license_finder
, store authoritative copies in your repo, and re-run audits whenever you upgrade ParadeDB.
Read the grant section of the license. Apache-2.0 and MIT generally allow commercial redistribution, but confirm any additional files (models, data) follow the same terms.
.
Yes. Current builds ship with an Apache-2.0 license unless noted otherwise. Always verify the commit you deploy.
No. Any user with the pg_read_server_files
role can use pg_read_file()
; otherwise, ask a DBA.