Add `pg-strom` — GPU acceleration extension for PostgreSQL
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 34
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hi 👋,
I’d like to suggest adding [pg-strom](https://github.com/heterodb/pg-strom) to the list of PostgreSQL extensions managed by this project.
pg-strom is a mature and well-maintained extension that enables GPU acceleration for SQL queries using NVIDIA CUDA. It significantly speeds up large-scale scans, joins, and aggregations, making it especially useful for analytical workloads and data warehousing scenarios.
🔍 Project Information
-
Name: pg-strom
-
Maintainer: HeteroDB, Inc.
-
License: GPL-2.0
-
Category: Performance / GPU Acceleration
-
Key Features:
- GPU-accelerated sequential scans, joins, and group-by
- Compatible with PostgreSQL 12–16
- CUDA 11+ support
- Transparent query planner integration (
GpuScan,GpuJoin, etc.)
💡 Why It’s Valuable
Including pg-strom would make this collection more complete for users seeking performance-oriented or GPU-enhanced PostgreSQL extensions.
It’s one of the few production-grade GPU integrations available for PostgreSQL today and could attract researchers or engineers working in high-performance computing (HPC), analytics, or AI data pipelines.
Would you consider adding this project?
I’d be happy to provide more details or help with the metadata if needed.
Thanks for maintaining this great collection! 🙏
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies the pg-strom repository and the metadata it proposes, but names no project file, entry point, or test. Locate the extension catalog format and existing PostgreSQL entries first, then add pg-strom with the stated metadata and verify it using the project's available checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100