Skip to content

Pg-status

v1.5.0 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 6mo Relational Databases
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

c docker high-availability high-load http-api lightweight
+10 more
master-replica microservice monitoring observability performance postgresql replication service-discovery sidecar sql

Summary

AI summary

Fixed data race in host status updates by replacing buffers with a single atomic field.

Full changelog

Fixed the data race when updating host status. There are no longer two buffers and a status pointer; instead, there's now a single atomic status field. Since it consists of just four bool values, it occupies only 4 bytes and is therefore lock-free.

The writer atomically updates the status of each host. Readers atomically load the status and can continue working with their local copy as long as needed. Atomic operations are now relaxed, since synchronization with non-atomic data is no longer required.

The only downside of this approach which I don't consider critical for this project is temporary inconsistency while the writer is updating all hosts: some hosts may already have the new data, while others still have the old data.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Pg-status

Get notified when new releases ship.

Sign up free

About Pg-status

All releases →

Related context

Beta — feedback welcome: [email protected]