Chase Granberry

Can you try it with a normal string and see what happens? Comparing to a datetime field would likely be an edge case currently. And if you're hosted on our...

@lifeiscontent I updated the title here to better reflect your request. We'll take a closer look.

You'll now get `system` message like: ```json { "channel":"any", "extension":"postgres_changes", "message":"Subscribing to PostgreSQL failed: {:error, {:subscription_insert_failed, %{\"event\" => \"*\", \"schema\" => \"public\", \"table\" => \"blah\"}}}", "status":"error" } ``` It's a...

Can you confirm the connection strings of each service? With Supabase I assume you're connecting directly to Postgres? Using port 5432? You may be using a pooler with one and...

Thanks! Yeah I've got it mostly there. This is now on our billing page: I tried unsuccessfully to overwrite the x-axis with my own. It's just the labels get a...

@olirice lmk if you want to chat about this. You could implement the same logic as Logflare Endpoints. Basically, subscribe to a query with an interval and and idle timeout....

@jsmestad thanks for this ... using your fork for now!

I'm made a few changes a while back that should have improved this quite a bit. Closing for now. How has this been for you all?

@NiklasPor > The event: `system` extension: `postgres_changes` message is fired every heartbeat This is fixed actually. The re-subscribe is triggered with `realtime.setAuth` on the client because after the heart beat...

@AntonOfTheWoods thanks for this! I think the workaround here would actually work very well. But it would definitely be nice for Realtime to automatically batch stuff for you when needed....