shouldiuse.io

Categories

VERDICT

Should I use Pgtune?

Tuning PostgreSQL config by calculator - pgtune.leopard.in.ua

Worth it. Anyone self-hosting Postgres should run their hardware specs through it once — it is free, fast, and beats guessing. Skip it if you are on managed Postgres or need measured, workload-specific tuning.

Confidence

High. Based on ~20 public sources; no formal ratings or paid reviews exist for this free tool.

Ratings

  • Value for money
  • Ease of use
  • Feature depth
  • Support qualityNo support model documented
  • Security postureNo security disclosures found

Pricing

$0

Free

ModelNot disclosed
Monthly feesNot disclosed
HardwareNot disclosed
Free tierYes

Best for

  • Self-hosted Postgres on VPS
  • DevOps bootstrapping new DB servers
  • First-pass config sanity check

Not for

  • Managed Postgres users — RDS/Cloud SQL lock most params
  • High-traffic teams needing measured, workload-specific tuning
  • Anyone wanting support, SLAs, or guarantees
  • Enterprise DBAs — they outgrow static calculators immediately

Gotchas - check before you buy

medium

Treat output as a starting point; validate against real workload metrics

medium

Guess: managed providers (RDS, Cloud SQL) restrict most of these settings

medium

Small-maintainer project; new Postgres versions land at maintainer's pace

low

Site's own /security page returns 404 — no published security info

Pros and cons

Pros

  • Completely free and open source; no account or upsell
  • Recommended in official docs from GitLab, OVHcloud, Fortinet, BMC
  • Generates a full from simple hardware inputs
  • Supports multiple workload profiles and recent Postgres versions

Cons

  • Static formulas; experts reject one-size-fits-all tuning
  • No support or SLA — community-maintained side project
  • Baseline only; deeper config work needs other tooling

Sources & method

Analyzed 10/04/2026 - 9 sources - No known vulnerabilities found in the sources reviewed.

official x4review x4security x1

Key stats

  • Value for money: 5/5

    Rating

  • $0

    Starting price

  • 9

    Sources

  • Analyzed

  • Value for money: 5/5. Free, open source, no account needed
  • Ease of use: 4/5. Enter hardware specs, copy generated config
  • Feature depth: 3/5. Static formula baselines, no workload measurement
  • Support quality. No support model documented
  • Security posture. No security disclosures found
  • $0 Price Free, open source on GitHub
  • 6+ Vendor doc citations GitLab, OVHcloud, Fortinet, BMC, Weblate, frepple
  • Up to 18 Postgres versions Per the tool's own URL parameters

Pricing

Free

$0

  • Web config calculator
  • Open source on GitHub
  • No account required

Security

No known vulnerabilities found in the sources reviewed.

What users say

Widely cited across vendor docs and forums as the default starting point for Postgres config, though some experts dismiss static tuning altogether.

“We don't believe much in such static tuning ...”
Hacker News

Companies that use it

  • GitLab³
  • OVHcloud⁴
  • Fortinet
  • BMC
  • Weblate

Companies that could

  • Aiven⁸ Uses DBtune instead
Full analysis

Based on ~20 public sources; no formal ratings or paid reviews exist for this free tool.

Free open-source Postgres config calculator. Great starting point, not real tuning. Zero risk, zero support.

Methodology

Based on ~20 public sources; no formal ratings or paid reviews exist for this free tool.

Sources

  1. PGTune — official sitepgtune.leopard.in.ua
    official
  2. le0pard/pgtune on GitHubgithub.com
    official
  3. GitLab — Tune PostgreSQL docsdocs.gitlab.com
    official
  4. OVHcloud — PostgreSQL VPS guideovhcloud.com
    review
  5. HN — static tuning skepticismnews.ycombinator.com
    review
  6. Severalnines — PGTune alternativesseveralnines.com
    review
  7. pgconfig.com — config API alternativepgconfig.com
    official
  8. DBtune — AI-powered Aiven tuningdbtune.com
    review
  9. PGTune security pagepgtune.leopard.in.ua
    security

Rate this review

Anonymous. You can change your vote.

Loading votes…

Comments

One queue. No nested comments. Give a display name first. Limit: 200 words per comment and 7 comments per day. You can edit or delete yours.

Save a name to write a comment.

0 / 200 words

No comments yet.