Each holds a session advisory lock (internal/infrastructure/postgres/ownership.go) and a second instance fails to start by design. Decide between warm-standby failover (a standby blocks on the lock and takes over when it frees) and active-active (drop single ownership, make writes safe under concurrency). Done when killing the active instance loses no accepted work and service resumes without an operator.
Each holds a session advisory lock (internal/infrastructure/postgres/ownership.go) and a second instance fails to start by design. Decide between warm-standby failover (a standby blocks on the lock and takes over when it frees) and active-active (drop single ownership, make writes safe under concurrency). Done when killing the active instance loses no accepted work and service resumes without an operator.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Each holds a session advisory lock (internal/infrastructure/postgres/ownership.go) and a second instance fails to start by design. Decide between warm-standby failover (a standby blocks on the lock and takes over when it frees) and active-active (drop single ownership, make writes safe under concurrency). Done when killing the active instance loses no accepted work and service resumes without an operator.