oliverrice

5 ms·

1.
Show HN: Richrs – Rust port of Python's Rich for beautiful terminal output(github.com)
2 points by oliverrice 9mo ago|0 comments
2.
by oliverrice 1y ago
One peice of tooling I've wanted for Vitess is for it to make recommendations about sharding keys based on the statistics it collects + query patterns. Seems like it's in the perfect location to collect the data for that and remov
3.
by oliverrice 1y ago
how are you thinking the differences between mysql and postgres will impact multigres vs vitess? The ones the jump to mind are - Postgres has transactional DDL vs auto-commit. Can that property be retained? - Postgres leans into extensions
4.
by oliverrice 2y ago
OrioleDB maintains a very small set of Postgres patches that are targeted for upstream. The storage engine that mitigates the need for vacuuming [1] is implemented in a standard Postgres extension, so that will still need to be installed by
5.
by oliverrice 2y ago
I don't want to hijack Datadogs+Quickwit's post comment section with unrelated promotional-looking info. Quick summary below but if you have any other questions pls tag olirice in a Supabase GH discussion. The OrioleDB storage eng
6.
by oliverrice 2y ago
(disclaimer: supabase employee) OrioleDB continues to be a fully open source and liberally licensed. We're working with the OrioleDB team to provide an initial distribution channel so they can focus on the storage engine vs hosting + p
7.
by oliverrice 2y ago
yeah, fair shout `columnar index` for hybrid analytical workloads and `multi-master` roadmap items haven't been put in an order on the schedule yet so maybe multi-master makes sense to do first. Both align with webscale requirements th
8.
by oliverrice 2y ago
what's your use-case for multi-master that would not be supported by something like regional routed for read-replicas with high availability? i.e. do you have a specific need for low global write latency, or is it motivated by somethin
9.
OrioleDB beta7: Benchmarks(orioledb.com)
140 points by oliverrice 2y ago|15 comments
10.
by oliverrice 2y ago
At Supabase we also recently switched to Nix for packaging our Postgres+extensions bundle https://github.com/supabase/postgres/blob/develop/flake.nix
11.
Postgres Bloat Minimization(supabase.com)
24 points by oliverrice 2y ago|1 comments
12.
Packaging Supabase with Nix(supabase.com)
15 points by oliverrice 2y ago|1 comments
13.
by oliverrice 2y ago
In Studio you'd need to click on a query to get the recommendations but the most important queries to optimize are on several metrics like "Most time consuming", "Most frequent", "Slowest execution" are so
14.
by oliverrice 2y ago
> I'm concerned about getting locked in Supabase is one of the most portable platforms out there. The whole stack is self-hostable and open source. All of the data are contained in Postgres. You're one pg_dump away from being a
15.
by oliverrice 3y ago
What additional tooling do you think would be needed to turn this concept into a maintainable stack with good UX for mid-to-large sized applications?
16.
by oliverrice 3y ago
hey, author here (although not of this feature) Exposing postgres functions through the GraphQL API has been one of our most frequent requests. I'm really looking forward to seeing what people are able to build with this flexibility. T
17.
by oliverrice 3y ago
hi, author here & happy to answer any questions Really looking forward to the next steps with vecs and would love to hear any thoughts about the `future ideas`. Mainly, what kind of interface would you like to see for adapters/tran
18.
Show HN: Supabase Vecs – vector client for Postgres(supabase.com)
10 points by oliverrice 3y ago|2 comments
19.
by oliverrice 3y ago
PostGIS is a native extension mostly written in C. Since there is no C trusted language it would be hard to fit PostGIS into the TLE paradigm Its less of a problem for well known and trusted extensions like PostGIS though because it comes p
20.
by oliverrice 3y ago
yeah, exactly. pgxn also houses native extensions, some of which may be TLE compatible. database.dev is trusted language extension specific We've reached out to David, who runs pgxn to see how we might collaborate and allow pgxn to be
21.
by oliverrice 3y ago
RDS does have the underlying native extension that is required to install user defined packages (pg_tle) from database.dev. It doesn't currently have support for the extension that is necessary to make the in-database client work to in
22.
by oliverrice 3y ago
index_advisor is a project that almost made the cut for LW7. We decided to launch it as a pgtle instead to get some feedback before we (spoiler) probably release it in LW8 It uses the hypopg package to very quickly generate an index for eac
23.
by oliverrice 3y ago
disclaimer: author of supabase/pg_graphql > What should AWS do -> provide Postgres or similar as a database choice If you're interested a postgres option you could check out Supabase GraphQL[1] which is based on pg_graphql [
24.
by oliverrice 4y ago
The 255 max length is something you could consider if untrusted people are able to insert data (through an API for example). A column in postgres can store up to 1 GB of data so its a possible DOS vector. Probably not an issue for most use-
25.
by oliverrice 4y ago
totally agree ""Using composite types is mildly annoying since you must wrap the composite column in parenthesis to access the field""" ^ yeah that is frustrating -- if you create domains over jsonb frequently, chec
26.
by oliverrice 4y ago
sure, if you switch the sql functions for plpgsql functions you can use procedural logic to on each segment and `raise exception` with a custom error message that will get returned to the client
27.
by oliverrice 4y ago
IIRC, hstore pre-dated jsonb. I'm not aware of any performance differences for the object type but it would be worth checking if you have a heavy workload. jsonb will tend to have better ORM support and it also isn't behind an ext
28.
by oliverrice 4y ago
while you always want to be careful with database load, that generally wouldn't be a concern for user defined types. In the example case, operating on the composite type would be more efficient than the string alternative for the most
29.
by oliverrice 4y ago
One of the restrictions of composite types is that they can not contain an instance of themselves. So unfortunately, this is not currently possible. I had this issue when trying to implement an AST type for pg_graphql[1] back when it was wr
30.
by oliverrice 4y ago
Agreed that there should be a data integrity or custom operation/filter/sorting requirement to motivate a user defined type

More ›