The command lists every database handled by ParadeDB on your PostgreSQL server.
Audit tasks, migration planning, and permission reviews often require a quick inventory of all ParadeDB-managed databases. Listing them helps confirm that expected environments—such as ecommerce_prod
and ecommerce_dev
—exist before you run schema changes.
Inside psql
, use the meta-command \l
(or \list
) to display every database, including those created by ParadeDB.Add +
for size and owner details.
Run SELECT datname FROM pg_database WHERE datallowconn;
to fetch names only. ParadeDB databases appear alongside regular ones, letting you filter or aggregate results.
If you suffix ParadeDB databases with _parade
, append AND datname LIKE '%\_parade'
to the catalog query.This pattern keeps the command extension-agnostic.
Wrap the catalog query in a Bash script using psql -tAc
. Your CI/CD pipeline can then confirm that ecommerce_prod
exists before running migrations on tables like Orders
or Products
.
Grant CONNECT
on each ParadeDB database only to roles that really need it.Over-permissive access can expose customer data contained in tables such as Customers
.
Use predictable names—e.g., shop_parade_prod
, shop_parade_stage
—so listing commands return an organized, sortable list.
.
No. \l is a psql meta-command. Use the catalog query in application code.
No. Reading pg_database is non-blocking and safe for production systems.