porro

End of life  /  PostgreSQL  /  6.3

End of life

PostgreSQL 6.3 is past end of life.

Security fixes stopped on 1 Mar 2003, 8643 days ago. New vulnerabilities in 6.3 won’t be fixed.

Released
1 Mar 1998
Active support
—
Security fixes
ended 1 Mar 2003
Latest
6.3.2

Upgrade to PostgreSQL 18: security fixes until 14 Nov 2030.

Release cycles

Every PostgreSQL cycle, at a glance.

Active support means bug fixes and security fixes; after it, security fixes only. Past the end of security support, nothing.

  1. 18
  2. 17
  3. 16
  4. 15
  5. 6.3
  • Active support
  • Security fixes only
  • Supported
  • Ends within 90 days
  • Ended
All 29 PostgreSQL cycles →

What to upgrade to

Go to 18, not 14.

14 runs out in 14 days. 18 is the newest supported PostgreSQL cycle, with security fixes until 14 Nov 2030.

Before you upgrade

A major upgrade needs pg_upgrade or a dump and restore. Try it on a copy of the database first. Read the PostgreSQL 18 upgrade guide

How to check your version

Which PostgreSQL is this site on?

In SQL

$ psql -c "SELECT version();"
PostgreSQL 17.6 on x86_64-pc-linux-gnu

On the server

$ psql --version
psql (PostgreSQL) 17.6
# that’s the client; the server can differ

Know before support ends.

Porro reads the PHP, framework and database version from every site and tells you 90 days before support runs out.

Start your free trial →

Dates from endoflife.date/postgresql, checked daily · data as of 29 Oct 2026.