Skip to content

active 2025-06-092026-05-17 (UTC)

Partial coverage12,384 / 14,093 hourly files (88%) · 2 absent upstream · 1,703 failed, retryable2024-12-312026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
653
Pushes
6
Pull requests
6
Issues
10
Stars
586
Forks
16

Activity over time

Daily event counts in the loaded window

Line chart, 343 days from 2025-06-09 to 2026-05-17. Pushes: 6 total, peak 2 in a day. Pull requests: 6 total, peak 1 in a day. Issues: 10 total, peak 4 in a day. Comments: 19 total, peak 3 in a day. Stars: 586 total, peak 167 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
sharmay18525
bdrouvotAWS16019
BRupireddy23000
ianthrive2002
ichi-7771000
umutoguz1000
jim-mlodgenski1001
prensgold1000
MonkeyGyu1010
MauroCL751001
yuito-tanaka1000
anth0nyleung1000
kustav1231001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#314sharmay2026-04-21 10:33
    Request : Support to Postgresql 18
  • Issue#315yuito-tanaka2026-04-16 05:10
    Multiple UNIQUE constraint violation error not logged/outputted (INSERT/INSERT Conflict)
  • Issue#310bdrouvotAWS2026-02-20 05:28
    PostgreSQL PANIC due to SMgrRelation hashtable corruption under pgactive active-active replication
  • Issue comment#310bdrouvotAWS2026-02-10 13:23
    PostgreSQL PANIC due to SMgrRelation hashtable corruption under pgactive active-active replication
  • Issue#306sharmay2026-01-01 17:59
    Replication fails during Patroni switchover (ShareUpdateExclusiveLock & Per-DB worker self-check failure)
  • Pull request#307MonkeyGyu2025-12-31 16:31
  • Issue comment#306jim-mlodgenski2025-12-31 14:04
    Replication fails during Patroni switchover (ShareUpdateExclusiveLock & Per-DB worker self-check failure)
  • Issue#306prensgold2025-12-31 13:25
    Replication fails during Patroni switchover (ShareUpdateExclusiveLock & Per-DB worker self-check failure)
  • Issue#305umutoguz2025-12-25 05:28
    ERROR: data for dropped column persists after re-adding the column manually
  • Issue comment#224sharmay2025-10-29 15:28
    Document pgactive_conflict_history table trimming
  • Issue#146sharmay2025-10-29 15:27
    Document how to do BDR log mining for errors/logs of interest with log_fdw
  • Issue#86sharmay2025-10-29 15:20
    Have how-to guides for common BDR use-cases
  • Issue#85sharmay2025-10-29 15:19
    Support pg_upgrade of pgactive members
  • Issue#63sharmay2025-10-29 15:18
    Run performance and memory consumption tests
  • Issue comment#303sharmay2025-10-16 14:09
    Add a check for PK
  • Pull request#303sharmay2025-10-15 13:43
  • Issue#302ichi-7772025-10-08 01:10
    How do I execute a trigger on the Subscriber side?
  • Pull request#300sharmay2025-08-13 20:31
  • Issue comment#145MauroCL752025-08-13 16:56
    Document an example for custom conflict triggers definition and use
  • Pull request#298sharmay2025-07-23 14:16
  • Pull request#299sharmay2025-07-21 14:34
  • Issue comment#296bdrouvotAWS2025-06-20 05:31
    docs: clarify database creation and connection step in quickstart
  • Issue comment#293kustav1232025-06-19 12:30
    Not able to Compile in Amla Linux 8
  • Issue comment#293sharmay2025-06-19 12:26
    Not able to Compile in Amla Linux 8
  • Issue comment#293ianthrive2025-06-16 07:25
    Not able to Compile in Amla Linux 8

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