PostgreSQL- Is It Postgre or Postgres?

The Short Answer

It's PostgreSQL. Not "Postgre." Not "Postgres." The official name is PostgreSQL, pronounced "post-gres-cue-ell."

But here's where it gets messy.

Why People Call It "Postgres"

Back in 1996, when PostgreSQL replaced the old POSTGRES name, the project team added SQL to reflect the database's query language. Smart move.

But "Postgres" stuck. Why? Three reasons:

• It's faster to type
• It's easier to say
• Old-timers remember the original name

Is "Postgres" Wrong?

No. It's an accepted alias. The PostgreSQL project itself recognizes "postgres" as a valid alternative. The command-line tool to start the database? It's literally called pg_ctl and postgres (the actual server binary)

You'll see "postgres" used constantly in documentation, tutorials, and production configs. It's not a mistake. It's just shorter.

What About "Postgre"?

Nobody calls it "Postgre." Stop doing that. It makes you look like you don't know what you're talking about.

The name comes from "Post-Ingres," the original database project at UC Berkeley. It's not "Postgre" anything.

How to Pronounce It

Here's the breakdown:

• PostgreSQL — "Post-gres-Cue-Ell"
• Postgres — "Post-gres"
• Never — "Post-gre" or "Post-gree"

Say it wrong and nobody will correct you to your face. But they'll notice.

The Naming Comparison

Getting Started: Which Name to Use

When you're setting up, connecting, or configuring:

• Use postgres as your default database name during installation
• The default superuser role is postgres
• Your connection string will look like: postgresql://user:pass@localhost:5432/postgres

When you're writing about it or explaining it to someone:

• Say PostgreSQL in blog posts, documentation, and resumes
• Say Postgres when chatting with developers
• Never say "Postgre" unless you're trying to confuse people

The Bottom Line

PostgreSQL. Postgres. Both work. Use the one that fits the context.

Just don't call it Postgre.