go-pg/pg

Golang ORM with focus on PostgreSQL features and performance

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 11th, 2026
Created on April 24th, 2013
Open Issues & Pull Requests: 124 (+0)
GitHub issues: Enabled
Number of forks: 415
Total Stargazers: 5,783 (+0)
Total Subscribers: 82 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.1 hours
Mean response time: 7.0 days
90th percentile: 21.2 days
Tracked items: 6

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,181 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

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

Top labels

  • enhancement (1)
  • feature (1)
  • help-wanted (1)
  • v11 (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

go-pg is a PostgreSQL client and ORM for Go that emphasizes PostgreSQL-specific features and performance optimization.

The tool addresses the need for type-safe database access in Go applications targeting PostgreSQL. It provides an object-relational mapping layer that translates Go structs into SQL queries while exposing PostgreSQL capabilities like JSONB and HStore types. The approach focuses on leveraging PostgreSQL's native strengths rather than abstracting them away, allowing developers to write efficient queries that take advantage of the database's advanced features.

Developers should be aware that go-pg is in maintenance mode, with only critical issues being addressed. The project's active development has shifted to Bun, a successor that maintains similar functionality while extending support to PostgreSQL, MySQL, MariaDB, and SQLite. For new projects, particularly those requiring multi-database compatibility, Bun is the recommended choice. go-pg remains suitable for existing PostgreSQL-focused applications or teams deeply invested in its API, and it continues to receive critical bug fixes. The ecosystem includes complementary tools for migrations, model generation, sharding, and monitoring integration.

Work in the issue tracker is dominated by feature requests, help-wanted issues, and enhancement proposals, indicating that the project maintains a backlog of potential improvements despite its maintenance status.