Why should you care?

A SaaS product on PostgresVerse might keep shared reference data in public while isolating each tenant module in its own schema for cleaner permissions.

See it live — copy this example

Run in pgAdmin or psql.

CREATE SCHEMA IF NOT EXISTS billing;
SET search_path TO billing, public;
CREATE TABLE billing.invoices (
  invoice_id bigserial PRIMARY KEY,
  amount numeric(12,2) NOT NULL
);

What happened?

• CREATE SCHEMA makes a namespace.
• search_path tells PostgreSQL where to resolve unqualified names.
• The table lives in billing, not public, so you can GRANT schema-level access later.

Practice next

1. Connect to PostgresVerse.
2. Run CREATE SCHEMA IF NOT EXISTS billing;
3. Run SET search_path TO billing, public;
4. Create schema analytics and move a test table with ALTER TABLE ... SET SCHEMA.
5. Run SHOW search_path; after changing it in pgAdmin.

Remember

Database = isolated catalog; schema = folder inside it. search_path controls default object lookup. Use schemas before multiplying databases.

PostgresVerse billing split

Finance wants invoices separated from catalog tables without a second database cluster.

Outcome: billing schema gets its own backup policy and read-only role.