How to Manage Users in ParadeDB in PostgreSQL

How do I manage users and permissions for ParadeDB in PostgreSQL?

The MANAGE USERS workflow in ParadeDB lets you create, alter, drop, and grant privileges to database roles so teams can safely query ParadeDB objects.

Welcome to the Galaxy, Guardian!

Oops! Something went wrong while submitting the form.

Description

Example H2

Example H3

Why would I manage users in ParadeDB?

Controlling who can read, write, and administer ParadeDB objects prevents accidental data changes and secures sensitive information. Well-scoped roles also keep query performance predictable.

Which PostgreSQL commands control ParadeDB users?

CREATE ROLE, ALTER ROLE, DROP ROLE, and GRANT are the core statements.ParadeDB stores its data in standard schemas, so normal PostgreSQL privilege rules apply.

How do I create a read-only ParadeDB user?

Create the role, revoke default rights, then grant SELECT on ParadeDB schemas.Use NOLOGIN service roles plus separate LOGIN roles for better security.

Step-by-step

1️⃣ CREATE ROLE parade_reader LOGIN PASSWORD '•••'; 2️⃣ REVOKE ALL ON SCHEMA public, paradedb FROM parade_reader; 3️⃣ GRANT USAGE ON SCHEMA paradedb TO parade_reader; 4️⃣ GRANT SELECT ON ALL TABLES IN SCHEMA paradedb TO parade_reader; 5️⃣ ALTER DEFAULT PRIVILEGES IN SCHEMA paradedb GRANT SELECT ON TABLES TO parade_reader;

How do I grant write access only to vector indexes?

Vector indexes live in the paradedb schema.Grant INSERT and UPDATE on the specific index tables while keeping other tables read-only.

Best practices for ParadeDB role design

Give every micro-service its own LOGIN role; bundle common privileges into NOLOGIN service roles; use ALTER DEFAULT PRIVILEGES so new indexes inherit permissions; audit roles quarterly.

Can I manage users in a transaction?

Yes. Wrap multiple GRANT and ALTER ROLE statements in BEGIN/COMMIT to ensure atomic permission changes.

How to revoke a user safely?

First REVOKE privileges, then DROP ROLE.This avoids orphaned objects owned by the user.

FAQs

Does ParadeDB require superuser rights?

No. Normal database owners can manage roles; superuser only needed for cluster-wide changes.

Will revoking USAGE on schema break existing connections?

Existing sessions keep their current search_path access until they reconnect.

Why How to Manage Users in ParadeDB in PostgreSQL is important

How to Manage Users in ParadeDB in PostgreSQL Example Usage


-- The application joins the ParadeDB vector index with Products
SELECT p.id, p.name, ivector.distance(v.embedding, query_vec) AS score
FROM Products p
JOIN paradedb.product_vectors v ON v.product_id = p.id
WHERE ivector.distance(v.embedding, ivector.embed('laptop')) < 0.2
ORDER BY score
LIMIT 10;

How to Manage Users in ParadeDB in PostgreSQL Syntax


-- Create a role that can query ParadeDB’s vector search tables
CREATE ROLE parade_reader LOGIN PASSWORD 'secret';
-- Remove default object creation rights
REVOKE CREATE ON SCHEMA public FROM parade_reader;
-- Grant minimal access to ParadeDB objects
GRANT USAGE ON SCHEMA paradedb TO parade_reader;
GRANT SELECT ON ALL TABLES IN SCHEMA paradedb TO parade_reader;
-- Ensure future ParadeDB tables stay visible
ALTER DEFAULT PRIVILEGES IN SCHEMA paradedb
    GRANT SELECT ON TABLES TO parade_reader;

-- Typical ecommerce context: allow app to join vector index with products
GRANT SELECT ON TABLE Products, paradedb.product_vectors TO parade_reader;

Common Mistakes

Granting ALL ON SCHEMA paradedb to every user. This lets users create and drop ParadeDB indexes. Fix: grant only USAGE or specific DML rights.
Forgetting ALTER DEFAULT PRIVILEGES. New ParadeDB tables become invisible to existing roles. Fix: set default privileges right after initial GRANT.