Why should you care?

A Flipkart price stored as float causes ₹99.99 to become ₹99.989999; numeric(10,2) and timestamptz for delivery slots avoid production incidents.

See it live — copy this example

Run in pgAdmin or psql.

CREATE TABLE products (
  product_id uuid PRIMARY KEY DEFAULT gen_random_uuid(),
  name text NOT NULL,
  price numeric(10,2) NOT NULL,
  tags text[] DEFAULT '{}',
  specs jsonb DEFAULT '{}'
);

What happened?

• uuid with gen_random_uuid() gives globally unique ids.
• numeric holds exact decimals.
• text[] stores tag lists.
• jsonb stores flexible specs with binary efficiency.

Practice next

1. Create products table in PostgresVerse.
2. Insert one row with tags ARRAY['electronics','sale'] and specs '{"warranty":"1y"}'::jsonb.
3. Select tags[1] and specs->>'warranty' to extract values.
4. Add a daterange column for promotion validity and insert '[2026-01-01,2026-03-01)'.
5. Cast a string to inet type for storing customer IP addresses.

Remember

numeric is for money; float is for science. jsonb indexes well; json is storage-only. Arrays and uuid reduce join complexity for tags and ids.

PostgresVerse catalog types

Merchandising stores variant specs in jsonb while keeping SKU price as numeric for GST calculations.

Outcome: Finance reports match payment gateway amounts to the paisa.