Ivan FBandClaude Opus 5 ee00a37d69 fix(postgres): stop a partition sequence when another instance holds the lock ...

Every DDL step took and released the advisory lock on its own, and a step
skipped because the lock was busy returned ok, so the caller walked on to the
next step believing the previous one had run. That is how a node ends up
dropping a constraint another instance already dropped -- a fatal error on a
sequence it never started. Tell "deferred" apart from "done" and abort the
whole sequence on the first deferral, leaving the work to the instance that
owns the lock.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-21 16:46:41 +02:00

..

api

fix(conf): default QUIC off on the messaging path (#4084)

2026-07-30 21:34:49 +01:00

channels

Rework logging to be useful (#4110)

2026-08-19 13:55:15 +02:00

messaging

Rework logging to be useful (#4110)

2026-08-19 13:55:15 +02:00

waku

fix(postgres): stop a partition sequence when another instance holds the lock

2026-08-21 16:46:41 +02:00

logos_delivery.nim

feat(ffi): pin nim-ffi 0.3.0 and stop the node on destroy (#4111)

2026-08-19 12:42:04 -03:00