Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kiwicopple
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
kiwicopple
1mo ago
> mirror data directly to Iceberg > I’d bet you’re likely to see this from a Postgres-specific provider first, like Supabase. we deprecated this feature in our ETL tool[0]. The functionality is still in there but we can't support
2.
▲
by
kiwicopple
2mo ago
Fwiw we wouldn’t take legal action but sometimes we politely reach out if the name could cause confusion for customers - everyone has been very amicable and usually it’s a win/win to rename anyhow
3.
▲
by
kiwicopple
2mo ago
(supabase cofounder) reach out if you need any help integrating. contact details are in my profile
4.
▲
Multigres Supports Listen/Notify Across Pooled Connections
(multigres.com)
3 points
by
kiwicopple
2mo ago
|
0 comments
5.
▲
by
kiwicopple
3mo ago
(supabase employee) confirming that we're still working hard on this. aiming to be production-ready this year. benchmarks and compatibility testing are on track
6.
▲
Are Memories Transferable – Or Edible?
(quantamagazine.org)
9 points
by
kiwicopple
3mo ago
|
0 comments
7.
▲
by
kiwicopple
3mo ago
Yes that’s how it will work. The transition will be seamless
8.
▲
by
kiwicopple
3mo ago
Hey HN, Supabase CEO The main highlight here is that we have released Multigres v0.1: https://supabase.com/blog/multigres-v0-1-alpha This is open source and self-hostable. It’s not production ready yet. That will take
9.
▲
by
kiwicopple
4mo ago
> Supabase is another one that was cool, but now it is in the AI abyss. (supabase ceo) I'm curious what gives you this impression? it's true that a lot of platforms build on top of Supabase, but our focus is still just building
10.
▲
by
kiwicopple
4mo ago
> It's infamously hard to exhaustively unit-test concurrency. a useful example from last week where TLA+ found a bug in pg_rewind: https://multigres.com/blog/2026/05/04/tla-pg-rewind
11.
▲
by
kiwicopple
5mo ago
Oriole is under very heavy development since we acquired them. We cut a release just 2 weeks ago: https://github.com/orioledb/orioledb/releases/tag/beta15 We expect it to be production ready this year
12.
▲
by
kiwicopple
5mo ago
clarifying a few misconceptions: > RLS policies are executed per row not necessarily. the planner integrates the policy expression into the query plan. stable/immutable expressions and indexable predicates aren't naively re-e
13.
▲
by
kiwicopple
7mo ago
> Why is there no InnoDB for PostgreSQL? (we maintain OrioleDB) Mostly because the TAM API isn't mature enough yet. Hopefully we can upstream more patches so that it's possible > undo-based MVCC storage engine project stall?
14.
▲
A 2.5x faster Postgres parser with Claude Code
(multigres.com)
9 points
by
kiwicopple
7mo ago
|
7 comments
15.
▲
by
kiwicopple
8mo ago
[Supabase CEO] I’m sure there could be questions, given the brevity of this blog post. I’m happy to answer anything specific I’ve been chatting to Dennis for a long time now and our product-ideas were very aligned. We will share more about
16.
▲
by
kiwicopple
8mo ago
(Supabase CEO) > The danger is when apps expose the service_role key (or the new sb_secret_... format) Fwiw, the new secret keys are automatically revoked if they are pushed to github, and github is progressively rolling out push protect
17.
▲
by
kiwicopple
9mo ago
(Note: we work closely with the clickhouse team so this is not to intended to detract from their launch, simply to point out maintained options.) Our CH wrapper is actively maintained, with push down, parameterized views, and async streamin
18.
▲
Show HN: Iceberg-JS, a TypeScript Client for the Apache Iceberg REST Catalog
(github.com)
5 points
by
kiwicopple
9mo ago
|
0 comments
19.
▲
by
kiwicopple
10mo ago
GitHub repo is here if you want to use this for self-hosted Postgres databases: https://github.com/supabase/wrappers
20.
▲
Show HN: Apache Iceberg FDW for Postgres
(fdw.dev)
1 points
by
kiwicopple
10mo ago
|
1 comments
21.
▲
by
kiwicopple
10mo ago
> get more Supabase Realtime back into the game if the price was more viable too feel free to reach out to me on twitter (same username) to discuss this if you want. we are starting to think of realtime in the context of gaming so if you
22.
▲
Open Data Standards: Postgres, OTel, and Iceberg
(supabase.com)
2 points
by
kiwicopple
10mo ago
|
0 comments
23.
▲
by
kiwicopple
11mo ago
impressive work jmo - thanks for open sourcing this (and OSI-compliant) we are working on a challenge which is somewhat like a homomorphic encryption problem - I'm wondering if OpenPCC could help in some way? : When developing websites
24.
▲
Generalized Consensus: Consistent Reads
(multigres.com)
4 points
by
kiwicopple
11mo ago
|
1 comments
25.
▲
by
kiwicopple
11mo ago
this is the last of a 9-part series on database consensus algorithms (like Paxos and Raft): > Raft improved accessibility but remains a monolithic algorithm that's risky to modify. This has effectively limited our flexibility in ad
26.
▲
by
kiwicopple
11mo ago
let me follow up with the team to find out what happened here
27.
▲
by
kiwicopple
11mo ago
hey DANmode - supabase ceo here. similar to the sibling thread I want to make sure I know what happened here: 1. someone created an website using supabase with email logins (and possibly edited the template / opt-out link) 2. som
28.
▲
by
kiwicopple
11mo ago
thanks for the tag lucasknight - i'll respond inline to OP about their email situation > your current AWS situation I think the assessment here is accurate: https://x.com/theo/status/1979271205279666586
29.
▲
by
kiwicopple
1y ago
fwiw, we have a team working on OrioleDB at supabase, with the plan to get to GA later this year or early next year. we'll continue to submit patches upstream for the TAM, and of course that will take as long as it takes for the commun
30.
▲
by
kiwicopple
1y ago
An alternative viewpoint which we are pretty open about in our docs: > our technological choices are quite different; everything we use is open source; and wherever possible, we use and support existing tools rather than developing from
More ›