Skip to content
Back to the index

PG Bloat Detective

github.comInfrastructure

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

PG Bloat Detective is an open-source PostgreSQL utility that checks table and index bloat and finds vacuum blockers. It can be installed with pip or Docker and is intended for database administrators and developers maintaining PostgreSQL systems.

Inferred · not functionally tested

Open SourceCLISelf-hosted
PG Bloat Detective preview
Visit github.com

Overview

6 features

Purpose: Diagnosing PostgreSQL storage bloat and vacuum blockers before they degrade database performance.

Inferred · not functionally tested

Audience: PostgreSQL database administrators and developers

Inferred · not functionally tested

Functions: monitoring

Inferred · not functionally tested

Interfaces: API: unknown · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

PG Bloat Detective is a Databases (SQL, NoSQL, vector, graph) project. Inferred · not functionally tested: It focuses on diagnosing PostgreSQL storage bloat and vacuum blockers before they degrade database performance. Inferred · not functionally tested: It is built as an open-source project for postgreSQL database administrators and developers. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: It runs on the command line, and it can be self-hosted.

It is developed by r69shabh. Inferred · not functionally tested: Among its 6 catalogued features are table bloat detection, index bloat detection, and vacuum blocker finding.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Table bloat detection
  • Index bloat detection
  • Vacuum blocker finding
  • PostgreSQL analysis
  • CLI usage
  • Docker deployment

Topics: Inferred · not functionally tested

Tags
postgresqldatabase-maintenancebloat-detectionvacuum-monitoring

JSON profile · Text profile · Access guide

Built with & integrations

Runs on
CLISelf-hosted

Trust & compliance

License
Open Source
Public signals
HTTPSOpen SourceFree tier

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 09:10 UTC
    PG Bloat Detective seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about PG Bloat Detective

What is PG Bloat Detective?
Inferred · not functionally tested: PG Bloat Detective focuses on diagnosing PostgreSQL storage bloat and vacuum blockers before they degrade database performance. It is catalogued under Databases (SQL, NoSQL, vector, graph) on PulseGate.
Who should use PG Bloat Detective?
Inferred · not functionally tested: PG Bloat Detective is an open-source project built for postgreSQL database administrators and developers.
Does PG Bloat Detective have a free plan?
Basis unknown · not verified: Yes — PG Bloat Detective is open source under the Open Source license and free to use.
What platforms does PG Bloat Detective run on?
Basis unknown · not verified: PG Bloat Detective runs on the command line. It can also be self-hosted.
Is PG Bloat Detective still maintained?
Unverified. PG Bloat Detective has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What projects are similar to PG Bloat Detective?
Similar projects tracked by PulseGate include Anumana, mcp-db-read-only, and DataBazaar.Anumanamcp-db-read-onlyDataBazaar
Who develops PG Bloat Detective?
PG Bloat Detective is developed by r69shabh.
Is PG Bloat Detective open source?
Basis unknown · not verified: Yes — PG Bloat Detective is open source under the Open Source license.

Also in Databases (SQL, NoSQL, vector, graph)

Same category — not a similarity match