Wen Bo Xie

@seriyps > 2. After having two db connections, one Postgrex conn (SELECT) and one epgsql conn (replication), everything is running fine. When I go into Observer and kill the Postgrex...

@seriyps Yea, `""` points to the `Realtime.Replication` process that's responsible for spinning up both Postgrex and epgsql processes.

@seriyps > Why there is a bunch of other processes started when you kill the postgrex process? `Realtime.Replication` has retry logic that spins up a new Postgrex process when an...

@seriyps no worries! Thank you so much for the help thus far!

@soedirgo can you please review the Rust portions of this PR whenever you have the bandwidth?

@mlanza thanks so much for reporting this issue. This is a server-side issue that we'll investigate and will post our findings here.

Related: https://github.com/supabase/realtime/issues/281

Hey everyone, sorry for taking so long to address this. For the new Multi-Tenant Realtime cluster that offers Broadcast and Presence functionalities, we wanted clients to immediately connect to the...

@EpicDevv we're still discussing internally about how to handle this but for the time being you can do what @GaryAustin1 suggested: ``` mySubscription = SBclient.channel(......).on(.......).subscribe (//error handler) mySubscription.socket.onMessage(message => {...

@fracek I left ya a couple of comments. Awesome work on this so far!!! 🔥