Oleksii Sholik

@kevin-dp the link is broken because someone disabled the Issues feature on the old repo. It was about making sure that a fully-qualified table name, i.e. one including the namespace,...

@magnetised Any advice on how ti address this?

I would argue against going to Postgres for name lookup. Replicating Postgres' identifier parsing is much simpler because it can be implemented as a pure function. Postgres is open source...

@Konrud could you share more of the log so we could see what was happening in the leadup to the error? You should also add the `ELECTRIC_LOG_LEVEL: debug` environment variable...

Checking the latest `main`, it definitely is more spammy than we would like to see: ``` 12:28:26.605 pid= [warning] Got connection/transport error when sending metrics %Mint.TransportError{reason: :econnrefused}, retrying... 12:28:26.606 pid=...

The error comes from elixir-otel-metric-exporter. I've opened a PR on that project - https://github.com/electric-sql/elixir-otel-metric-exporter/pull/9.

Testing Electric with telemetry export enabled but no connectivity to the telemetry endpoint yields expected error logs and no disruption of service. I wanted to test what happens when simulating...

Funny how our info-level logs include the publication name but the errors do not and neither do they mention the source ID.

Yeah, a lot has changed since this was originally reported.

I wanted to note that with the LockConnection's initialization now also async, the following error may get logged more frequently: ``` 17:23:08.783 pid= [debug] Starting replication client for stack single_stack...