The Morning Dev

Only the news worth knowing

‹
 
  • AAPL 344.17 ▼ 1.53%
  • MSFT 535.93 ▼ 3.58%
  • NVDA 181.60 ▼ 9.26%
  • GOOGL 282.57 ▼ 2.20%
  • AMZN 260.21 ▼ 2.19%
  • META 605.08 ▼ 3.96%
  • TSLA 343.69 ▼ 10.77%
  • AVGO 291.53 ▼ 10.43%
  • TSM 353.10 ▼ 10.78%
  • ORCL 115.16 ▼ 6.93%
  • AMD 404.40 ▼ 17.26%
  • NFLX 65.56 ▼ 1.25%
  • CRM 222.41 ▼ 2.07%
  • ADBE 246.44 ▼ 0.82%
  • INTC 52.25 ▼ 10.33%
  • IBM 247.11 ▼ 2.84%
  • PLTR 154.99 ▼ 9.73%
  • SNOW 269.54 ▼ 7.25%
  • NET 244.51 ▼ 8.28%
  • SAP 243.53 ▲ 1.45%

News

PostgreSQL 14 stops on November 12: test your old dumps first

DEV Community: backend · By Jules Robineau ·

On 12 November 2026, PostgreSQL 14 gets its final release. After that date, no more fixes, not even for a security flaw. One week later, PostgreSQL 19 is due to ship as a final release. Prepare your upgrade before support ends. Before you pick 18 or 19, ask yourself a simple…

The Brief

  • PostgreSQL 14 gets its final release on 12 November 2026.
  • After that date, PostgreSQL 14 receives no more fixes, including for security flaws.
  • PostgreSQL 19 is due as a final release one week later.

Why it matters

Teams running PostgreSQL 14 will have no security patches once support ends, so they need to plan and test an upgrade before that date.

Who’s affected

  • Teams running PostgreSQL 14

What to do

  1. Prepare the upgrade from PostgreSQL 14 before support ends
  2. Test old dumps before upgrading
  • PostgreSQL 14
  • PostgreSQL 18
  • PostgreSQL 19
  • #postgresql
  • #database
  • #end-of-life
  • #upgrade
  • #backend

Timeline

  1. DEV Community: backend

    PostgreSQL 14 stops on November 12: test your old dumps first

  2. PostgreSQL 14 final release; no more fixes after this date

  3. PostgreSQL 19 due as final release

How do you feel about this?

0 Comments

    More in Backend

    Outage

    GitHub Was Down for 8 Hours. Retries Made It Worse.

    In August, GitHub went down for almost eight hours. It started when one part of its system got overloaded. Then everything that couldn’t connect kept trying again, all at the same moment. All that extra traffic made it even harder for GitHub to recover. In one case, the retries…

    DEV Community: backend · The Unmeshed Team ·