Incident brief
Duplicate function
CREATE FUNCTION fails when a function with the same name and argument types already exists; CREATE OR REPLACE updates it instead of colliding.
In 10 seconds
- What
- Duplicate function
- What triggers it
- CREATE FUNCTION with a name and argument-type list that already exists.
- The fix
- Use CREATE OR REPLACE FUNCTION to update the existing definition.
- Proof
- Reproduced on PostgreSQL 18.4 → A CREATE FUNCTION reproduces SQLSTATE 42723 against the existing same-signature function.
The fix
What to do right now
The immediate, application-level response to this error.
- Use CREATE OR REPLACE FUNCTION to update the existing definition.
- Or change the argument types to define a genuinely different overload.
-- Update in place with CREATE OR REPLACE FUNCTION.
CREATE OR REPLACE FUNCTION add_one(int) RETURNS int LANGUAGE sql AS 'SELECT $1 + 1';Diagnose
See it live on the server
Run these against the affected instance to confirm the diagnosis before you act.
Standard triage — not specific to this error
These are canonical PostgreSQL system-catalog queries, shown as SQL to run. No sample output is attached because this is general triage, not a captured lab transcript.This SQLSTATE does not have an error-specific live snapshot yet. These are the canonical system-catalog queries you run against the affected server to see the problem in real time — standard triage, not a reproduced transcript.
What is running right now
Active backends, how long each has been running, and what it is waiting on.
SELECT pid,
state,
wait_event_type,
wait_event,
now() - query_start AS running_for,
left(query, 80) AS query
FROM pg_stat_activity
WHERE state <> 'idle'
AND pid <> pg_backend_pid()
ORDER BY running_for DESC NULLS LAST;Who is blocking whom
Turn raw blocking PIDs into the actual queries on both sides of the wait.
SELECT blocked.pid AS blocked_pid,
blocked.query AS blocked_query,
blocking.pid AS blocking_pid,
blocking.query AS blocking_query
FROM pg_stat_activity AS blocked
JOIN LATERAL unnest(pg_blocking_pids(blocked.pid)) AS b(pid) ON true
JOIN pg_stat_activity AS blocking ON blocking.pid = b.pid
WHERE cardinality(pg_blocking_pids(blocked.pid)) > 0;Locks that are still waiting
Every lock a backend has requested but not yet been granted.
SELECT l.pid,
l.locktype,
l.mode,
l.granted,
COALESCE(c.relname, l.transactionid::text) AS object
FROM pg_locks l
LEFT JOIN pg_class c ON c.oid = l.relation
WHERE NOT l.granted
ORDER BY l.pid;Why it happens
What PostgreSQL is telling you
The mechanism behind the error, grounded in the official manual — not paraphrased.
PostgreSQL 18 Documentation — Appendix A. PostgreSQL Error Codes (Table A.1, Class 42 — Syntax Error or Access Rule Violation)
42723 → duplicate_functionRead the full section on postgresql.org →
Recreating an existing function signature
A function 'add_one' with the same argument types already exists, so a plain CREATE FUNCTION raises 'function add_one already exists with same argument types'.The session continues normally
The failing statement ran outside a transaction block, so nothing was left in a bad state — the next statement in the same connection runs normally.Reproduce & verify
A real, single-session PostgreSQL reproduction
A literal transcript of SQL run against a live PostgreSQL instance in an isolated lab — the commands below are exactly what was executed.
- 1CREATE FUNCTION with a name and argument-type list that already exists.
- 2PostgreSQL matches the existing function by name and argument types.
- 3The duplicate is rejected with SQLSTATE 42723.
A migration re-declared an existing function without OR REPLACE and collided on the identical signature.
CREATE FUNCTION add_one(int) RETURNS int LANGUAGE sql AS 'SELECT $1 + 1';CREATE FUNCTION add_one(int) RETURNS int LANGUAGE sql AS 'SELECT $1 + 2';SELECT 'ok' AS session_after_error;What PostgreSQL actually returned
CREATE FUNCTIONERROR: function "add_one" already exists with same argument types session_after_error
---------------------
ok
(1 row)The definition applies cleanly with CREATE OR REPLACE.
We rerun the definition with CREATE OR REPLACE to show it updates in place.
Without this
Before: a duplicate CREATE FUNCTION aborts
With this, tested
After: CREATE OR REPLACE updates it
What Pro unlocks here
- The exact prevention SQL — copy-paste ready
- Raw psql output captured from the Docker lab
- A senior-DBA action list to take it further
- Live monitoring queries to catch it in production
- The deeper audit: fix-that-fails counterexample, GUC before/after, server-log evidence
Related & next steps
Follow the thread
Everything this error touches — jump straight to the sibling error, term, runbook, or parameter.
Verification
- Last verified
- 2026-07-24 (isolated lab, PostgreSQL 18.4)
- Reviewed by
- Verified against PostgreSQL 18.4 in an isolated lab environment
- Audit status
- reviewed