How PostgreSQL's NOTIFY Queue Fills Up and How to Clear It

·13 views

A developer reproduced the PostgreSQL 'too many notifications in the NOTIFY queue' error using PostgreSQL 17, Docker, and a deliberately limited queue size of 512 KiB set via the max_notify_queue_pages parameter. With a listener session held idle inside an open transaction, 100 large pg_notify() calls were issued from a second connection, filling the queue entirely after 64 successful sends and causing 36 to fail. The key finding is that an open transaction on the listener side blocks notification cleanup, regardless of how large the queue is configured. Simply committing the idle transaction allowed all pending notifications to be delivered and the queue usage returned to zero. This demonstrates that raising max_notify_queue_pages only delays the problem — the real fix is ensuring listener transactions do not remain open unnecessarily.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Laramod: A Lightweight Laravel Module System Built for Large Applications

A developer has released Laramod, a Laravel package designed to organise large applications into self-contained feature modules, each holding its own routes, controllers, models, migrations, and views. The tool addresses a common pain point where growing Laravel projects end up with hundreds of loosely related files sorted by type rather than by feature or purpose. Laramod was built after the author found existing solutions such as nWidart/laravel-modules and Laramod's lighter alternative too heavy or insufficiently flexible for their workflow. The package aims to let developers register a module with a single line, keep module configuration transparent and readable, and treat installed Composer packages identically to local modules. It draws conceptual inspiration from Django's app-based architecture and is designed to work with plain Laravel conventions without introducing proprietary abstractions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Short-Lived AI Agent Tokens Can Limit Damage From Leaked Credentials

A September 2026 VentureBeat report found that exposed AI agent credentials were used to breach 395 organizations, highlighting how long-lived machine-to-machine tokens create serious security gaps. Unlike human passwords, AI agent credentials often remain valid for hours or days, meaning a leaked token stays exploitable long after it is compromised. A developer tested two agent configurations against identity provider Kinde — one using a static token valid for 24 hours and another that automatically rotates its token every 120 seconds before expiry. The rotating agent ensures that any stolen copy of its token becomes useless within minutes, dramatically shrinking the window of exposure. Both agents use the standard OAuth client-credentials flow, with Kinde's per-application token lifetime settings — not the grant type itself — determining how quickly each token expires.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds 227,000-Match Football Odds Analysis Pipeline Using LLM Architecture

A developer spent six months building an open-source football data analysis pipeline called PitchQuant, processing over 227,000 historical matches to study what signals exist within betting odds. The system combines de-vigging, ELO ratings, Dixon-Coles Poisson modelling, and Kelly criterion calculations, with an LLM coordinating a strict multi-step inference process governed by 34 knowledge files and 238 automated checks. By combining individually weak statistical signals with calibrated weighting and rigorous backtesting, the pipeline improved directional accuracy from 48% to roughly 55%. Key findings include that Asian handicap movement is a stronger indicator than European odds alone, and that low-odds favourites with shallow handicap shifts win far less often than assumed. The project, released under an MIT licence on GitHub, is intended solely for academic research and explicitly does not claim to predict match outcomes.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Automation gap exposed: manual browser step silently stalled a 7-post cross-publishing queue

A five-step content cross-posting pipeline stalled for 72 hours with seven unmirrored articles, even though all automated components remained fully operational. The bottleneck was step four — a human or agent manually pasting content into a browser editor — which had been deliberately kept manual after the target platform moved its write API to a paid tier in May. The team had built automation around every adjacent task, shrinking the manual step to its minimum, but the manual step itself was simply not being completed. A monitoring system correctly flagged the backlog in amber for days, yet each session reviewing the dashboard assumed responsibility lay elsewhere since the automated steps were all green. The incident highlighted a process failure rather than a technical one: an amber alert requiring human action was repeatedly deferred because no session owned the incomplete manual step.

0 comments Read more at DEV Community