skills.rest
dmzoneill
dmzoneillCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug-local-db

Diagnose PostgreSQL and SQLite database issues in Podman containers.

2|Updated Feb 16, 2026
Search Tags:#database#postgresql#debug#sqlite#local#podman
One-click install
npx skills add https://github.com/dmzoneill/skills --skill debug-local-db
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-local-db
Source: https://github.com/dmzoneill/skills/tree/main/debug-local-db
Command: npx skills add https://github.com/dmzoneill/skills --skill debug-local-db

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and resolve issues with local or ephemeral databases, including PostgreSQL and SQLite, often running within Podman containers.

Core Features & Use Cases

  • Containerized DB Debugging: Inspect logs and versions of PostgreSQL databases running in Podman.
  • Database Health Checks: Analyze active connections, query activity, and lock contention.
  • Schema & Data Inspection: Dump database schemas and query table information.
  • Use Case: When your local development PostgreSQL database becomes unresponsive, this Skill can help identify if it's due to too many connections, long-running queries, or container issues.

Quick Start

Debug issues with the local PostgreSQL database, dumping the schema if necessary.

Frequently Asked Questions about debug-local-db

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a local PostgreSQL database running in a Podman container?▼

To debug a local PostgreSQL database in a Podman container, inspect container logs, check database versions, and analyze active connections. You can also review query performance and lock contention to identify unresponsiveness or connection exhaustion issues.

What causes a local PostgreSQL database to become unresponsive during development?▼

A local PostgreSQL database becomes unresponsive due to too many active connections or long-running queries. Container issues or lock contention within the database can also cause performance bottlenecks during local development sessions.

Can I inspect the database schema of a SQLite instance using this debugging approach?▼

Yes, you can inspect SQLite database schemas by dumping the full schema and querying table information. This allows for detailed analysis of local SQLite instances to diagnose structural or data-related issues.

Does this database debugging method work with both SQLite and PostgreSQL in ephemeral environments?▼

Yes, this database debugging method works with both SQLite and PostgreSQL instances in ephemeral environments. It specifically targets local databases managed via Podman containers to diagnose and resolve issues.

What is the best way to check for lock contention and active connections in a local database?▼

The best way to check for lock contention and active connections in a local database is performing health checks that analyze query activity. Database health checks inspect active connections and lock states to pinpoint performance issues.

Related Skills

Explore More Software Engineering Skills→
interflownexinterflownex
2

alloydb-omni-container

Manage AlloyDB Omni database container lifecycles in Docker or Podman.

Community
Intermediate
nimadorostkarnimadorostkar
25

database-performance

Analyze execution plans and query logs to resolve database latency and throughput issues.

Community
Advanced
JeffallanJeffallan
10.9k

database-optimizer

Diagnose slow queries and optimize indexes for PostgreSQL and MySQL.

Community
Advanced
shalevaminshalevamin

database-optimizer

Analyze execution plans and optimize PostgreSQL and MySQL database performance.

Community
Advanced