Even partial, biased download data is still useful. It can show which PG major versions are active. It can show which OS targets matter. It can show whether a package cell is used enough to justify maintenance. But be careful. A package with few downloads may still be important. Maybe we need a combined signal — stars, pageviews, availability, build failures, and downloads — something like a DB-Engines-style score for Postgres extensions.

Part III : The Delivery Layer

What We Can Still Infer

PIGSTY
Table 2

Distro Family

Combined path-only requests from repo.pigsty.io and repo.pigsty.cc.

56.1% DEB/APT
vs
39.7% EL/RPM
DEB/APT
362,61356.1%
EL/RPM
256,63739.7%
Other
26,6664.1%

Signal: DEB/APT leads the request mix, while RPM remains large enough to justify first-class repo work.

Table 4

PostgreSQL Major

Only requests where the path or package name identifies the PG major.

PG 17
73819.2%
PG 16
71518.6%
PG 14
69718.1%
PG 15
67417.5%
PG 13
67217.4%
PG 18
3579.3%

Signal: PG 17 is first, but active demand is spread across five older majors plus PG 18.

Table 5

Supported OS Versions

Selected path-only OS targets; unsupported zero-count rows are omitted.

EL 8
48,58610.5%
EL 9
132,46228.5%
EL 10
41,0868.9%
Debian 12
47,33910.2%
Debian 13
53,42111.5%
Ubuntu 22.04
49,15910.6%
Ubuntu 24.04
91,91219.8%

Signal: EL 9 and Ubuntu 24.04 carry the strongest visible demand in the selected OS set.