proxy: triple logging of some errors

[koivunej]

In nightly prodlike benchmark.

2024-09-17T07:57:45.038233Z ERROR connect_request{protocol=tcp session_id=25a984bf-8c2f-4eca-bb6c-68cf3385c675 peer_addr=3.20.172.197 ep=ep-orange-boat-w11dj1ty role=neondb_owner}:connect_to_compute: could not connect to compute node error=Postgres(Error { kind: Db, cause: Some(DbError { severity: "FATAL", parsed_severity: Some(Fatal), code: SqlState(E3D000), message: "database \"neondb\" does not exist", detail: None, hint: None, position: None, where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("postinit.c"), line: Some(1019), routine: Some("InitPostgres") }) })
2024-09-17T07:57:45.045597Z ERROR connect_request{protocol=tcp session_id=25a984bf-8c2f-4eca-bb6c-68cf3385c675 peer_addr=3.20.172.197 ep=ep-orange-boat-w11dj1ty role=neondb_owner}:connect_to_compute: couldn't connect to compute node error=Postgres(Error { kind: Db, cause: Some(DbError { severity: "FATAL", parsed_severity: Some(Fatal), code: SqlState(E3D000), message: "database \"neondb\" does not exist", detail: None, hint: None, position: None, where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("postinit.c"), line: Some(1019), routine: Some("InitPostgres") }) }) num_retries=1 retriable=false
2024-09-17T07:57:45.045674Z ERROR connect_request{protocol=tcp session_id=25a984bf-8c2f-4eca-bb6c-68cf3385c675 peer_addr=3.20.172.197 ep=ep-orange-boat-w11dj1ty role=neondb_owner}: per-client task finished with an error: Couldn't connect to compute node: db error: FATAL: database "neondb" does not exist

connect_to_compute: could not connect to compute node

neon/proxy/src/proxy/connect_compute.rs

Line 142 in b719d58

error!(error = ?err, "could not connect to compute node");

connect_to_compute: couldn't connect to compute node

neon/proxy/src/proxy/connect_compute.rs

Line 194 in b719d58

error!(error = ?e, num_retries, retriable = false, "couldn't connect to compute node");

Found while looking all warnings and errors in the eu-west-1 region. I later gave up on that idea :)

Expectation is that that a single error would only be logged once, and at least here it seems per session id that the same action was logged three times.