Zach a31e476623 fix: make boundary usage telemetry collection atomic (#21907) ...

Previously, UpsertBoundaryUsageStats (INSERT...ON CONFLICT DO UPDATE) and
GetAndResetBoundaryUsageSummary (DELETE...RETURNING) could race during
telemetry period cutover. Without serialization, an upsert concurrent with the
delete could lose data (deleted right after being written) or commit after the
delete (miscounted in the next period). Both operations now acquire
LockIDBoundaryUsageStats within a transaction to ensure a clean cutover.

2026-02-06 09:52:17 -07:00

..

doc.go

fix: handle boundary usage across snapshots and flush races (#21805)

2026-02-02 09:11:54 -07:00

tracker_test.go

fix: make boundary usage telemetry collection atomic (#21907)

2026-02-06 09:52:17 -07:00

tracker.go

fix: make boundary usage telemetry collection atomic (#21907)

2026-02-06 09:52:17 -07:00