How to Uninstall ParadeDB in PostgreSQL

Why remove ParadeDB from your database?

ParadeDB is great for vector search, but if you no longer need it or plan to migrate, uninstalling keeps the catalog lean and simplifies future upgrades.

What roles can uninstall ParadeDB?

Only a superuser or the database owner can execute DROP EXTENSION. Other roles must request elevated rights or ask the extension owner to run the command.

What is the exact DROP EXTENSION syntax?

Use DROP EXTENSION [IF EXISTS] paradedb [CASCADE | RESTRICT];. IF EXISTS prevents errors if the extension is missing. CASCADE drops dependent objects; RESTRICT (default) blocks the drop when dependencies exist.

How do I uninstall ParadeDB safely?

1) Connect to the target DB. 2) Ensure no active sessions rely on ParadeDB. 3) Back up objects that reference the extension. 4) Run the command within a transaction.

BEGIN;
DROP EXTENSION IF EXISTS paradedb CASCADE;
COMMIT;

How can I confirm ParadeDB is gone?

Query pg_extension. No row named paradedb means success.

SELECT * FROM pg_extension WHERE extname = 'paradedb';

Will my ecommerce tables stay intact?

Dropping the extension never alters regular tables like Customers, Orders, or Products unless they hold ParadeDB-based indexes. Inspect pg_indexes first.

Best practices before removal?

Dump the schema, drop dependent indexes manually for control, and test in staging. Always wrap the operation in a transaction.

Common mistakes and how to avoid them

dependency_exists: add CASCADE after evaluating impact. must be owner: switch to a superuser or extension owner.

Full ecommerce example

Assume Products has a ParadeDB vector index:

CREATE INDEX products_name_vec_idx
ON Products USING paradedb_ivfflat (to_tsvector('simple', name));

To uninstall ParadeDB safely:

BEGIN;
DROP INDEX IF EXISTS products_name_vec_idx;
DROP EXTENSION paradedb CASCADE;
COMMIT;