Skip to content

cybertec-postgresql/pg_squeeze

View on GitHub ↗Related repositories →

A PostgreSQL extension for automatic bloat cleanup

active 2023-11-202026-06-05 (UTC)

Partial coverage18,651 / 23,950 hourly files (78%) · 2 absent upstream · 5,296 failed, retryable2023-11-182026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
201
Pushes
6
Pull requests
2
Issues
17
Stars
126
Forks
3

Activity over time

Daily event counts in the loaded window

Line chart, 929 days from 2023-11-20 to 2026-06-05. Pushes: 6 total, peak 1 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 17 total, peak 4 in a day. Comments: 44 total, peak 8 in a day. Stars: 126 total, peak 4 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

ContributorContributionsPushesPRsComments
ahouska215016
kovmir13027
ramkly8005
Barre7006
df7cb6102
shruthikc-gowda4003
xydoublez3002
mobilephone7242001
damianzawadzki1001
devrimgunduz1000
lincoln3101001
tcartwright1000
NitinJadhav-postgres1000

Recent activity

Latest issues, pull requests and releases

  • Issue#91df7cb2026-04-30 09:42
    REPACK in PG v19
  • Issue comment#91ahouska2026-04-29 19:11
    REPACK in PG v19
  • Issue comment#90xydoublez2025-11-24 09:01
    pg_squeeze 1.9 on PostgreSQL 16.5 repeatedly causes missing btree entries for composite non-unique index on small table
  • Issue comment#90xydoublez2025-11-24 00:53
    pg_squeeze 1.9 on PostgreSQL 16.5 repeatedly causes missing btree entries for composite non-unique index on small table
  • Issue#90xydoublez2025-11-21 03:04
    pg_squeeze 1.9 on PostgreSQL 16.5 repeatedly causes missing btree entries for composite non-unique index on small table
  • Issue comment#88ahouska2025-10-08 10:32
    Adjust code for PostgreSQL 12 EOL
  • Pull request#89kovmir2025-10-08 09:50
  • Issue comment#87df7cb2025-09-15 15:37
    Control File Version Mismatch for pg_squeeze v1.9.0
  • Issue#87NitinJadhav-postgres2025-09-15 10:20
    Control File Version Mismatch for pg_squeeze v1.9.0
  • Issue comment#78df7cb2025-08-04 13:28
    initial slot snapshot too large
  • Issue#78df7cb2025-08-04 13:28
    initial slot snapshot too large
  • Issue#85df7cb2025-08-04 13:23
    squeeze worker uses lots of memory
  • Issue comment#80Barre2025-02-22 17:43
    ERROR: Incompatible DDL or heap rewrite performed concurrently
  • Issue#80Barre2025-02-22 17:29
    ERROR: Incompatible DDL or heap rewrite performed concurrently
  • Issue comment#79Barre2025-01-23 00:27
    Segmentation fault
  • Issue comment#79Barre2025-01-22 05:07
    Segmentation fault
  • Issue comment#78ahouska2025-01-02 13:35
    initial slot snapshot too large
  • Issue#78ramkly2024-12-27 12:54
    initial slot snapshot too large
  • Issue comment#76ahouska2024-12-15 19:29
    Duplicate key value violates unique constraint
  • Issue comment#76ahouska2024-12-14 19:46
    Duplicate key value violates unique constraint
  • Issue comment#76Barre2024-12-13 20:54
    Duplicate key value violates unique constraint
  • Issue comment#76Barre2024-12-13 07:26
    Duplicate key value violates unique constraint
  • Issue comment#76Barre2024-12-13 07:20
    Duplicate key value violates unique constraint
  • Issue comment#76ahouska2024-12-13 07:00
    Duplicate key value violates unique constraint
  • Issue comment#75ahouska2024-09-24 11:18
    PostgreSQL 17 support

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 126 stars here means stars gained during the window, not the repo's star count.