A PostgreSQL extension to add a collection data type
active 2024-11-18 → 2026-07-31 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 621 days from 2024-11-18 to 2026-07-31. Pushes: 34 total, peak 4 in a day. Pull requests: 9 total, peak 2 in a day. Issues: 35 total, peak 3 in a day. Comments: 20 total, peak 3 in a day. Stars: 5 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| jim-mlodgenski | 71 | 34 | 4 | 16 |
| artsolo-db | 14 | 0 | 0 | 2 |
| sibowu-aws | 8 | 0 | 3 | 2 |
| akos2 | 2 | 0 | 0 | 0 |
| Deepesh125 | 1 | 0 | 1 | 0 |
| ahmed-shameem | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#19jim-mlodgenski2026-03-06 21:11Support integer indexes in pgCollection
- Issue#43jim-mlodgenski2025-12-11 22:00Direct assignment (`:=`) to INOUT pgCollection parameter raises type error
- Issue#36jim-mlodgenski2025-12-11 19:26`INOUT` parameter fails with uninitialized collections but works with empty collections
- Issue#41jim-mlodgenski2025-11-06 18:05`add()` does not release memory for replaced items, leading to memory leak and OOM risk
- Issue comment#41jim-mlodgenski2025-11-06 18:05`add()` does not release memory for replaced items, leading to memory leak and OOM risk
- Issue#42jim-mlodgenski2025-11-06 18:04Direct assignment (`:=`) between pgCollection instances crashes backend and disconnects all sessions
- Issue#42artsolo-db2025-10-16 16:38Direct assignment (`:=`) between pgCollection instances crashes backend and disconnects all sessions
- Issue#42artsolo-db2025-10-16 16:38Direct assignment (`:=`) between pgCollection instances crashes backend and disconnects all sessions
- Issue#41artsolo-db2025-10-16 14:40`add()` does not release memory for replaced items, leading to memory leak and OOM risk
- Issue#35jim-mlodgenski2025-09-24 12:19Inconsistent JSON parsing behavior: scalar entries treated same as object entries in collection
- Issue#38jim-mlodgenski2025-09-24 02:12Collection JSON Parsing Allows Duplicate Keys
- Pull request#39jim-mlodgenski2025-09-24 02:12
- Pull request#40sibowu-aws2025-09-23 19:10
- Pull request#39sibowu-aws2025-09-23 18:22
- Issue comment#34jim-mlodgenski2025-09-23 13:42Crash with transferring collection via INOUT parameter in repeated procedure calls
- Issue#31jim-mlodgenski2025-09-23 00:06Inconsistent `key not found` error behavior across uninitialized, empty, and non-empty collections
- Pull request#37jim-mlodgenski2025-09-22 18:40
- Issue comment#37sibowu-aws2025-09-22 18:17Fix use-after-free in collection delete operations
- Issue comment#37jim-mlodgenski2025-09-22 16:48Fix use-after-free in collection delete operations
- Pull request#37sibowu-aws2025-09-21 18:32
- Issue#36artsolo-db2025-09-20 13:26`INOUT` parameter fails with uninitialized collections but works with empty collections
- Issue#35sibowu-aws2025-09-17 18:41Inconsistent JSON parsing behavior: scalar entries treated same as object entries in collection
- Issue comment#25jim-mlodgenski2025-09-16 22:06Use-After-Free: Server Crash When Accessing Iterator After Element Deletion
- Issue comment#25jim-mlodgenski2025-09-15 21:55Use-After-Free: Server Crash When Accessing Iterator After Element Deletion
- Issue comment#25sibowu-aws2025-09-15 18:40Use-After-Free: Server Crash When Accessing Iterator After Element Deletion
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 5 stars here means stars gained during the window, not the repo's star count.