How to Use CURRENT_USER in PostgreSQL

How do I use CURRENT_USER in PostgreSQL?

CURRENT_USER returns the role name executing the current SQL statement.

Welcome to the Galaxy, Guardian!

Oops! Something went wrong while submitting the form.

Description

What does CURRENT_USER return?

The CURRENT_USER keyword returns the role name that owns the current SQL session. Its value is fixed at parse time, so it does not change inside the same transaction, even after SET ROLE.

Why use CURRENT_USER in everyday work?

Audit scripts, debug permission errors, and build security-definer functions by logging or branching on the active role. Knowing who ran a query speeds up compliance checks.

How do I call CURRENT_USER?

Call it like any scalar expression:

SELECT CURRENT_USER;

You can embed it in SELECT, INSERT, UPDATE, DELETE, views, triggers, and constraints.

Example: include CURRENT_USER in an insert

INSERT INTO Orders_Audit(order_id, ran_by) SELECT id, CURRENT_USER FROM Orders WHERE order_date >= CURRENT_DATE - INTERVAL '1 day';

Can I alias CURRENT_USER?

Yes. Use an alias for clearer column names:

SELECT CURRENT_USER AS executed_by;

Best practices for CURRENT_USER

Compare CURRENT_USER, SESSION_USER, and USER to understand role switching. Avoid relying on it inside SECURITY DEFINER functions unless you need the caller’s identity.

Why How to Use CURRENT_USER in PostgreSQL is important

How to Use CURRENT_USER in PostgreSQL Example Usage


BEGIN;
-- Confirm the role that will own the new order
SELECT CURRENT_USER AS session_role;

-- Create a new order for customer 42
INSERT INTO Orders(customer_id, order_date, total_amount)
VALUES (42, CURRENT_DATE, 99.99);
COMMIT;

How to Use CURRENT_USER in PostgreSQL Syntax


-- Basic usage
SELECT CURRENT_USER;

-- Aliased output
SELECT CURRENT_USER AS executed_by;

-- Inside a larger statement
INSERT INTO Orders_Audit(order_id, ran_by)
SELECT id, CURRENT_USER
FROM Orders
WHERE order_date >= CURRENT_DATE - INTERVAL '1 day';

Common Mistakes

Calling <code>CURRENT_USER()</code> with parentheses. It is a special SQL keyword, not a function. Omit the parentheses: <code>SELECT CURRENT_USER;</code>.
Assuming <code>CURRENT_USER</code> changes after <code>SET ROLE</code>. It is fixed at parse time. Use <code>SESSION_USER</code> or <code>USER</code> to see the new active role.