Skip to content
Signalcrest
Back to feed
hackernewsdevtools

Postgres LISTEN/NOTIFY actually scales

Postgres scales with LISTEN/NOTIFY

Steady
Signal score
14
as of 45d ago
Sources
4
agreeing on postgres
Trajectory
Too early
needs a few more snapshots

Why this scored 14

every term, weighted
Velocity+1.3 / 40

Engagement gained per hour since the last capture, against the fastest item on its own source

Acceleration+0.0 / 25

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+8.3 / 25

How many independent communities are talking about the same entity

Recency+7.9 / 10

Decays to zero over 14 days

Saturation penalty3.4 / 30

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite14.1

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic'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

Signal history

7-day window (free)
Not enough history yet — the trend line fills in as snapshots accrue (every 30 min).

Entities

postgres
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/hn%3A49040296)](https://www.signalcrest.app/topic/hn%3A49040296)

Drop this in a README or blog post — it updates automatically as the score moves.