You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If start_postgres fails with error!("could not start the compute node: {:#}", err); it returns None as child handle, which makes wait_postgres do nothing, which then starts sync-safekeepers in cleanup_after_postgres_exit before postgres exited, leading to spurious fighting over terms.
If start_postgres fails with
error!("could not start the compute node: {:#}", err);
it returns None as child handle, which makeswait_postgres
do nothing, which then starts sync-safekeepers incleanup_after_postgres_exit
before postgres exited, leading to spurious fighting over terms.ref https://neondb.slack.com/archives/C03H1K0PGKH/p1740668117244159?thread_ts=1740665903.645719&cid=C03H1K0PGKH
The text was updated successfully, but these errors were encountered: