Hacker ApprovedDepartments

pg_durable

Shares rank 5 of 14 Postgres extensions by recommenders

Adds durable, resumable workflows inside PostgreSQL so teams can skip a separate orchestration system. Critics say embedding SQL between dollar-quotes makes the code hard to read, test and version.

Adds durable, resumable workflows inside PostgreSQL so teams can skip a separate orchestration system. Critics say embedding SQL between dollar-quotes makes the code hard to read, test and version.

16 people gave an opinion

recommend it
10
criticize it
6
approval share
63%
Each figure is one person. RecommendsCriticizes

Recommended in 1 of 13 months

  1. November 2025: not recommended
  2. December 2025: not recommended
  3. January 2026: not recommended
  4. February 2026: not recommended
  5. March 2026: not recommended
  6. April 2026: not recommended
  7. May 2026: not recommended
  8. June 2026: recommended
  9. July 2026: not recommended
  10. August 2026: not recommended
  11. September 2026: not recommended
  12. October 2026: not recommended
  13. November 2026: not recommended (month in progress)

Why it doesn’t carry the badge

  • 10 people recommend itNeeds 10 or more, met.
  • 1.6 recommenders for every criticNeeds 2 to 1 or better, not met.
  • Recommended in 1 of 13 monthsNeeds 4 or more, not met.

The same three rules apply to every product, and the badge can’t be bought. How the badge works

What people say about it

The reasons people give, with the number of comments that give each one. Open a reason to read what they said.

Why people recommend it

Each mark is one comment

  • Durable, resumable long-running jobs

    “pg_durable brings the same reliability and durablity semantics to long running operations within the database.”

    Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

    “Seems like an interesting idea to add durability and resumability to lengthy cron jobs.”

    Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

What people warn about

Each mark is one comment

  • SQL embedded in code is hard to read

    “I’d rather stay out of messy SQL land for something like this if I can avoid it”

    Comment from 6 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

    “Not sure I love the syntax and the way SQL is embedded between the $$”

    Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

    “it's very bizarre to try and read this”

    Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”
  • Doubts it is the right approach

    “These approaches always suffer from the same issues such as synchronous single threaded code”

    Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

    “This feels like the wrong solution to an age old problem”

    Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

    “Before this I thought it was impossible to surpass Perl.”

    Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”
  • Workflow logic kept inside database

    “you've now got the problem that there are apparently two sources of truth for that bit of the code”

    Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

    “not a fan of keeping complex flows inside the DB”

    Comment from 6 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

Other Postgres extensions people recommend

The four most recommended other Postgres extensions, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.

pg_durable compared with 4 alternatives
ProductRecommendCriticizeApprovalMonthsOwnedBadge
pgvector552073%10—Approved
PostGIS20387%8—Approved
pg_lake18386%5—Approved
ParadeDB13193%8—Approved
pg_durableThis page10663%1——
See all 14 Postgres extensions, ranked

What people said

16 of the 17 comments that mention it, newest first. Each links to the original comment.

“not a fan of keeping complex flows inside the DB”

CriticizesComment from 6 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“I’d rather stay out of messy SQL land for something like this if I can avoid it”

MixedComment from 6 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“Because you likely already have a database and likely don't need to bring on an entire new distributed system to orchestrate your workflows.”

RecommendsComment from 6 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“You can’t unit test it. You can’t version it.”

MixedComment from 6 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“These approaches always suffer from the same issues such as synchronous single threaded code”

CriticizesComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“Before this I thought it was impossible to surpass Perl.”

CriticizesComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“They think they can vibecode PG19.”

CriticizesComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“pg_durable brings the same reliability and durablity semantics to long running operations within the database.”

RecommendsComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“you've now got the problem that there are apparently two sources of truth for that bit of the code”

CriticizesComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“The advantage is probably that you can track the exact state of the job in the database itself”

MixedComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“Seems like an interesting idea to add durability and resumability to lengthy cron jobs.”

RecommendsComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“Not sure I love the syntax and the way SQL is embedded between the $$”

MixedComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“Snapshot PITR of your database means everything restores including the durable jobs at the PIT.”

RecommendsComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“seen it substantially reduce code and increase reliability”

MixedComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“it's very bizarre to try and read this”

MixedComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

“This feels like the wrong solution to an age old problem”

CriticizesComment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution”

Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.