For Developers

Unix Timestamp in SQL

How to get and convert Unix timestamps in SQL — with the actual syntax differences between PostgreSQL, MySQL, and SQLite side by side, since each one does this differently.

Get the current timestamp

-- PostgreSQL
SELECT EXTRACT(EPOCH FROM NOW());

-- MySQL
SELECT UNIX_TIMESTAMP();

-- SQLite
SELECT strftime('%s', 'now');

Timestamp → date

-- PostgreSQL
SELECT TO_TIMESTAMP(1750000000);

-- MySQL
SELECT FROM_UNIXTIME(1750000000);

-- SQLite
SELECT datetime(1750000000, 'unixepoch');

Date → timestamp

-- PostgreSQL
SELECT EXTRACT(EPOCH FROM TIMESTAMP '2025-06-15 12:00:00');

-- MySQL
SELECT UNIX_TIMESTAMP('2025-06-15 12:00:00');

-- SQLite
SELECT strftime('%s', '2025-06-15 12:00:00');

The SQL-specific pitfall

There is no standard SQL function for this — every engine invented its own, and the return types don't match. PostgreSQL's EXTRACT(EPOCH FROM ...) returns a double precision (fractional seconds included), MySQL's UNIX_TIMESTAMP() returns an integer or decimal depending on the input, and SQLite's strftime('%s', ...) returns a string that many drivers won't auto-cast for you in a WHERE clause comparison. If a query moves between engines — migrations, ORMs targeting multiple databases, or copy-pasted Stack Overflow snippets — check the return type explicitly rather than assuming it behaves like the last engine you used.

Have a timestamp right now?

Paste it into the Timestamp ⇄ Date Converter to check it instantly, in any timezone, without writing any code. Working across several languages on the same project? The full Epoch Time in Programming Languages guide has all of them side by side for quick comparison.

Unix Timestamp in SQL

The SQL-specific pitfall

Have a timestamp right now?

Related tools & reading

Epoch Time in Programming Languages

Timestamp ⇄ Date Converter

Storing Dates in Postgres and MySQL