plpgsql
for database engineers
Why this scored 8
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Outlook
low confidence · estimate, not a guarantee7-day
~8
range 0–20
14-day
~8
range 0–23
30-day
~8
range 0–27
Signal history
7-day window (free)projected trajectory (estimate, not a guarantee)
The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 132
PL/pgSQL LOOP two times over function result set without re-evaluating it
Shows how to loop over PL/pgSQL results efficiently without extra queries. · for database engineers
stackoverflowSteady 3 · postgresdata6d ago - 23
Problem with plpgsql trigger during update table with triggered column
Trigger issue in PostgreSQL · for postgres admins
stackoverflowSteadydata57d ago