Skip to content

Pg-status

v1.6.0 Feature

This release adds 3 notable features for engineering teams evaluating rollout.

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

Hosts are marked possibly dead after failed requests and trigger immediate failover if a new master exists.

Full changelog

If a host doesn't respond to a request, it could mean either a temporary issue or that the host is actually down.
To avoid marking a host as dead prematurely, a host is only considered dead after pg_status__max_fails attempts.

To speed up our reaction to possible host unavailability, if a host doesn't respond and the number of attempts
hasn't yet exceeded pg_status__max_fails, we mark it as possibly dead, and this affects which hosts get returned:

  • If the current master is marked as possibly dead and there’s already a new master, we immediately switch to the new master.
  • When selecting a replica, preference is given to live hosts. However, if no live replicas meet a search criteria, a
    potentially dead replica will be returned. This means that for up to pg_status__max_fails attempts, the
    fairness of load balancing between replicas can be disrupted.

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]