chasers

5 ms·

1.
by chasers 2y ago
Not a free car because I paid them. Funny enough their dashboard showed a payment so I just screenshot that for them to look up in their own db!
2.
by chasers 2y ago
Rivian lost my full payment for an R1S.
3.
by chasers 3y ago
btw recently cleaned up my wal cache busting code quite a bit if you're interested. https://github.com/Logflare/logflare/blob/main/lib/logflare/... Need to make a lib out of this!!
4.
by chasers 3y ago
I've helped with this one. Happy to answer any questions also.
5.
by chasers 3y ago
We use :telemetry to collect usage data per tenant for Supabase Realtime. We do this for rate limiting but it also makes it very easy for us to attach a listener ( https://github.com/supabase/realtime/blob/main
6.
by chasers 3y ago
We just had some orphaned database connections (our bug) to a tenant and were able to find and kill them because of Erlang's observability: https://gist.github.com/chasers/e4aa33625e6ea39ecb89f03383dd... edit: lin
7.
by chasers 3y ago
Yo :D This is what Supabase Realtime does! https://github.com/supabase/realtime Spin up a Supabase database and then subscribe to changes with WebSockets. You can play with it here once you have a db: https:/&#x2
8.
by chasers 3y ago
supabase dev here... this was a very fun load test to run. happy to answer any questions. shoutout to José Valim and the Dashbit team for the help on Supavisor. elixir and erlang are amazing tools. connection limits, even with pgbouncer, ha
9.
by chasers 3y ago
yes otel across all of Supabase in on our radar for sure. we just added ingest support for otel payloads to Logflare (docs coming soon) so when we have that you'll get them on the platform and locally. if you haven't seen the metr
10.
by chasers 3y ago
> although ensuring that only a single client is writing to a database at any time is (mostly) left to the application Sounds like trouble.
11.
by chasers 3y ago
Yeah as in zero ops needed. Maybe NoOps.
12.
by chasers 3y ago
I hadn't seen WalEx. Looks rad!!
13.
by chasers 3y ago
Phoenix.PubSub is basically a noop service. It really just works. If discovering nodes is difficult in your env, try using a listen/notify libcluster strategy: https://github.com/supabase/supavisor/blob/m
14.
by chasers 3y ago
Triggers can affect throughput quite a bit on busy tables. And we didn't want people schemas polluted with triggers. But also we use Erlang distribution and Phoenix.PubSub because with a global network clients connected to the same nod
15.
by chasers 3y ago
Accepting pull requests if anyone is interested :D
16.
by chasers 3y ago
Happy Livebook user here! Congrats on all the new stuff this week. Really great work.
17.
by chasers 3y ago
Also fwiw, if this is self-hosted I'm sure you can export them from BigQuery in an acceptable format. And if this is Supabase hosted, you can reach out to support and we can do that for you. Log drains is high on the list for the hoste
18.
by chasers 3y ago
I work on logs at Supabase. What format(s) would you need?
19.
by chasers 3y ago
For sure > https://github.com/supabase/supavisor/issues/69
20.
by chasers 3y ago
Appreciate the detailed feedback here. Frankly these are all things I've wanted to address. We've just had to prioritize other tasks. We're definitely going to keep iterating. Thanks for taking the time to try it!
21.
by chasers 3y ago
Wow man Quickwit looks amazing. Probably would have reached for it when I started Logflare if it was around. I have not seen anything open source that really separates compute and storage like that in one package. You can setup Clickhouse t
22.
by chasers 3y ago
Depends on your use case. If the volume of data you're looking at is not much, Sentry is more feature rich and refined. If you want to expose a logging interface to your customers and/or easily integrate large volumes of structure
23.
by chasers 3y ago
Yes! You can sign up for Logflare separately actually.
24.
by chasers 3y ago
> Can you point out ways in which Logflare uses it that makes it so (for ex, is it tiered-storage with a BQ front-end)? After 3 months BigQuery storage ends up being about half the cost of object storage if you use partitioned tables and
25.
by chasers 3y ago
Curious how was it awful for you? Really have not regretted any part of using BigQuery.
26.
by chasers 3y ago
I’m thinking can just use :erlang.phash2 to pin a client connection process to a db connection process. The only thing is a slow query could block a db connection for others pinned to it.
27.
by chasers 3y ago
> Elixir's Ecto can (and that Go example) so if you use Elixir (or Go) you can use prepared statements with PgBouncer (or Supavisor!) in transaction mode. Ah `binary_parameters` is just this Go lib thing. Ecto just sends unnamed pre
28.
by chasers 3y ago
That doesn't say anything about named vs unnamed. This does though: "If successfully created, a named prepared-statement object lasts till the end of the current session, unless explicitly destroyed. An unnamed prepared statement
29.
by chasers 3y ago
Not yet but we definitely are going to do that.
30.
by chasers 3y ago
I will say that we are trying to keep the connection to the database open as long as possible and only disconnect when necessary. PgBouncer's db connections are more dynamic. So if Postgres is doing query plan caching by session then c

More ›