How to fix ERROR: type 'typename' does not exist in PostgreSQL

What this error means

The "type does not exist" error (error code 42704) appears when PostgreSQL's query parser or function compiler encounters a reference to a data type that it cannot locate in the current schema or the search path. PostgreSQL allows custom types such as enums, composite types, and domain types to be defined within schemas. When you reference a custom type in a stored procedure, function declaration, or variable assignment, PostgreSQL must be able to locate that type. If the type is defined in a non-public schema, it must be explicitly qualified with the schema name, or the schema must be in the search_path. If the type name is misspelled, the type hasn't been created yet, or it was created in a different schema than you're searching, PostgreSQL will report that the type does not exist.

Typical symptoms

• Stored procedure or function fails with ERROR: type 'typename' does not exist
• Function definition succeeds but fails when called with custom type parameters
• Declaring a variable with a custom type fails at runtime
• Error occurs after schema migration or type creation
• Type works in one database session but not another

Common causes

1. Custom type not fully qualified with schema name (e.g., public.my_type instead of just my_type)
2. Custom type defined in a non-public schema that is not in the search_path
3. Typo or misspelling in the custom type name
4. Custom type does not exist in the database yet
5. Enum type name mismatch (e.g., looking for 'enum_name_enum' when actual type is 'name_enum')
6. Using a non-PostgreSQL type like STRING instead of PostgreSQL-compatible type like TEXT
7. Type created in a different schema than where the function is defined
8. Function references a type before it is created in migration order

How to fix "ERROR: type 'typename' does not exist"

\dT

\dT public.*
\dT myschema.*

SELECT type_name, type_schema
FROM information_schema.user_defined_types
WHERE type_schema NOT IN ('pg_catalog', 'information_schema')
ORDER BY type_schema, type_name;

-- Type defined in 'myschema' schema
CREATE TYPE myschema.user_record AS (
  id INT,
  name TEXT
);

-- Function fails if type is not qualified
CREATE FUNCTION get_user() RETURNS user_record AS $$
BEGIN
  -- ERROR: type "user_record" does not exist
END;

-- Correct - fully qualified type name
CREATE FUNCTION get_user() RETURNS myschema.user_record AS $$
DECLARE
  result myschema.user_record;
BEGIN
  result.id := 1;
  result.name := 'John';
  RETURN result;
END;
$$ LANGUAGE plpgsql;

-- If user_record is in public schema, this works
CREATE FUNCTION get_user() RETURNS user_record AS $$
BEGIN
  -- This is fine for public schema types
END;

-- View the current search_path
SHOW search_path;

-- Set search_path to include your schema
SET search_path TO myschema, public;

-- Now you can reference types without full qualification
CREATE FUNCTION get_user() RETURNS user_record AS $$
BEGIN
  -- Works now because myschema is in search_path
END;

-- For a specific user
ALTER USER myuser SET search_path = myschema, public;

-- For a specific database
ALTER DATABASE mydatabase SET search_path = myschema, public;

-- Check what enum types exist and their exact names
SELECT typname, typtype FROM pg_type
WHERE typtype = 'e'
ORDER BY typname;

-- If your enum is named this:
CREATE TYPE account_access_permissions_enum AS ENUM (
  'read', 'write', 'admin'
);

-- And your function looks for this (wrong):
CREATE FUNCTION check_permission(p account_access_permissions)
RETURNS BOOLEAN AS $$
BEGIN
  -- ERROR: type "account_access_permissions" does not exist
END;

-- Correct - matches the exact enum name
CREATE FUNCTION check_permission(p account_access_permissions_enum)
RETURNS BOOLEAN AS $$
BEGIN
  -- Works now
  RETURN p = 'admin';
END;
$$ LANGUAGE plpgsql;

-- Wrong - STRING type doesn't exist in PostgreSQL
CREATE TYPE user_record AS (
  name STRING
);
-- ERROR: type "string" does not exist

-- Correct - use TEXT instead
CREATE TYPE user_record AS (
  name TEXT
);

-- Or use VARCHAR with a length limit
CREATE TYPE user_record AS (
  name VARCHAR(255)
);

-- Migration 001_create_types.sql
CREATE TYPE public.user_record AS (
  id INT,
  name TEXT
);

-- Migration 002_create_functions.sql
CREATE FUNCTION get_user() RETURNS public.user_record AS $$
BEGIN
  -- Works because type was created in previous migration
END;
$$ LANGUAGE plpgsql;

-- Wrong order - function before type
CREATE FUNCTION get_user() RETURNS public.user_record AS $$
-- ERROR: type "user_record" does not exist

Advanced notes

CREATE TYPE audit.change_record AS (
  table_name TEXT,
  operation TEXT,
  timestamp TIMESTAMP
);

CREATE PROCEDURE log_change(change audit.change_record) AS $$
BEGIN
  INSERT INTO audit.log VALUES (change.table_name, change.operation, change.timestamp);
END;
$$ LANGUAGE plpgsql;

-- If user_record type is in myschema, select from it like this:
SELECT * FROM CAST('{1, "John"}' AS myschema.user_record);

-- Or use the fully qualified name in any type context
CAST(value AS myschema.custom_type)

CREATE TYPE person AS (id INT, name TEXT);
CREATE TYPE employee AS (person person, salary NUMERIC);

-- Use in function
CREATE FUNCTION get_employee() RETURNS employee AS $$
DECLARE
  emp employee;
BEGIN
  emp.person.id := 1;
  emp.person.name := 'Alice';
  emp.salary := 50000;
  RETURN emp;
END;
$$ LANGUAGE plpgsql;

-- Create a domain
CREATE DOMAIN valid_email AS TEXT CHECK (VALUE ~ '^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}$');

-- Use it like any other type
CREATE TABLE users (email valid_email);

-- Also reference it fully if in non-public schema
CREATE FUNCTION validate_email(e myschema.valid_email) RETURNS BOOLEAN AS $$
BEGIN
  RETURN e IS NOT NULL;
END;
$$ LANGUAGE plpgsql;

Frequently asked questions

What does "42704" mean?

The "type does not exist" error (error code 42704) appears when PostgreSQL's query parser or function compiler encounters a reference to a data type that it cannot locate in the current schema or the search path. PostgreSQL allows custom types such as enums, composite types, and domain types to be defined within schemas. When you reference a custom type in a stored procedure, function declaration, or variable assignment, PostgreSQL must be able to locate that type.

How do I fix "42704"?

This error occurs when PostgreSQL cannot find a custom type referenced in a function, procedure, or variable declaration. Common causes include missing schema qualification of custom types, incomplete migrations, enum type naming mismatches, or using non-PostgreSQL-compatible types like STRING instead of TEXT.

What causes "42704"?

Custom type not fully qualified with schema name (e.g., public.my_type instead of just my_type) Custom type defined in a non-public schema that is not in the search_path Typo or misspelling in the custom type name

Is the "42704" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• Type "typename" does not exist

  How to fix "Type does not exist" in PostgreSQL

  MEDIUM

• Triggered data change violation

  How to fix "Triggered data change violation" in PostgreSQL

  HIGH

• Unable to establish connection

  How to fix "Unable to establish connection" in PostgreSQL

  HIGH

• Triggered action exception

  How to fix "Triggered action exception" in PostgreSQL

  HIGH

• Invalid password

  How to fix "Invalid password" in PostgreSQL

  HIGH

• FATAL: no pg_hba.conf entry for host

  How to fix 'FATAL: no pg_hba.conf entry for host' in PostgreSQL

  HIGH

Official resources & further reading

• 📚PostgreSQL Official Documentation
• 📖
  PostgreSQL Error Codes(Official Docs)
• 📖
  PostgreSQL User-Defined Types(Official Docs)
• 📖
  PostgreSQL CREATE TYPE Documentation(Official Docs)
• 🐙
  Error 42704: Type does not exist - npgsql(GitHub)
• 🐙
  Type does not exist with procedure parameters - jOOQ(GitHub)