supabase-community/postgres-language-server

A Language Server for Postgres

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 46 minutes ago
Added to GitGenius on September 13th, 2026
Created on May 17th, 2023
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 126
Total Stargazers: 5,254 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.0 hours
Mean response time: 33.5 days
90th percentile: 62.9 days
Tracked items: 150

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Work labelled "bug" is answered fastest, typically in about 12 hours, while "enhancement" waits about 4 weeks. Only 12% of issues opened in the past year have been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 4
Closed in 7 days: 0
Avg open age: 353 days
Stale 30+ days: 15
Stale 90+ days: 13

Recent activity

Opened in 7 days: 4
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (100)
  • enhancement (11)
  • good first issue (10)
  • documentation (9)
  • contributors wanted (3)
  • help wanted (1)

Detailed Description

Postgres Language Server is a language server protocol implementation for Postgres that brings IDE-like developer tooling to SQL development.

The tool addresses the lack of reliable, standardized SQL tooling by implementing the Language Server Protocol for Postgres. It uses Postgres' own parser, libpg_query, to guarantee 100% syntax compatibility with actual Postgres behavior. The server-client architecture with transport-agnostic design means developers can access its features through multiple interfaces: the standard LSP for editor integration, a command-line interface, HTTP APIs, and a WebAssembly module. This multi-interface approach makes the tooling accessible across different development workflows and environments.

Developers working with Postgres should consider this tool if they want autocompletion, hover information, syntax diagnostics, type checking through EXPLAIN error insights, SQL formatting, and linting capabilities—including both migration linting and database linting. It also provides PL/pgSQL support. The tool integrates with VSCode, Cursor, Neovim, Zed, and Sublime Text, so adoption depends on your editor of choice. Anyone building Postgres-focused development infrastructure or seeking to standardize SQL tooling across a team will find the multi-interface design particularly valuable, as it avoids lock-in to a single editor or transport mechanism.

Development activity shows consistent engagement with the codebase, with regular updates addressing both features and maintenance. The project maintains active documentation and provides clear installation and getting-started resources. Community contributions are welcomed through the standard GitHub workflow, and the project acknowledges its dependencies on foundational work from related projects in the tooling ecosystem.