kelvich

7 ms·

1.
by kelvich 9mo ago
This thread seems to reflect how the HN audience has shifted — less commenters know what `ssh example.com` does and more commenters concerned about privacy policy.
2.
by kelvich 9mo ago
> I'm not going to SSH to a random server. Opening a random website likely exposes you to more risk.
3.
by kelvich 2y ago
To provide more context, our original plan was to launch the GA on March 22nd. However, we decided to move the date to April 15th because a few projects required additional time to complete. Last week we saw Supabase announcement but we did
4.
Fork() takes more than a second! how so?(neon.tech)
2 points by kelvich 3y ago|0 comments
5.
by kelvich 3y ago
Thank you, point taken. The blog post does mention memory limitations, but we could elaborate more on the fact that the index is entirely in-memory and clarify the user-visible consequences of this fact. We'll edit the post for better
6.
by kelvich 3y ago
Yes, exploring http/3 is on the roadmap. One of the learnings for us was the fact that v8 is quite good with caching open TCP connection; For consecutive queries the same TCP+TLS session is being reused. Even when queries are sent from
7.
by kelvich 3y ago
There is a second network interface attached to each pod and that interfaces are connected to vxlan-based overlay network. So during the migration VM can keep the same ip address (APR will take care of traffic finding it's destination)
8.
by kelvich 3y ago
Main idea was one branch per pull request to better test migrations on a fresh data. But one branch per dev or branch per dev per pr will also work.
9.
by kelvich 3y ago
> The article ends with the statement that you are pretty much done here for now. Would optimizing your TLS termination not maybe offer some more ways to speed this up? Or is that also already fully optimized? No, we don't do early
10.
by kelvich 4y ago
Feel free to try it out on https://neon.tech/
11.
by kelvich 4y ago
Gotcha. I drew my conclusion based on the mentioned package.json. Now wonder why did you decide to go with rust for query engine? Do you compile it into wasm?
12.
by kelvich 4y ago
https://github.com/prisma/prisma/blob/main/packages/client/p...
13.
by kelvich 4y ago
Another angle here is compatibility. With our current driver one can use ordinary node-postgres package, as we can substitute TCP-related calls with WebSocket calls during the build time. With that it possible to use all the packages that d
14.
by kelvich 4y ago
Right, that is one of the use cases. Auth is tricky part in that setup -- in the browser user may change the query in arbitrary way. But there are some workarounds like obtaining JWT from 3rd party service and checking it via Row-Level Secu
15.
by kelvich 4y ago
It is possible to create branch retroactively
16.
Postgres over WebSockets for Cloudflare Workers(blog.cloudflare.com)
4 points by kelvich 4y ago|0 comments
17.
by kelvich 4y ago
And some other projects that DARPA worked on: https://spectrum.ieee.org/tech-history/space-age/the-bunny-t...
18.
by kelvich 4y ago
Licklider is one the main persons behind the ARPANET. The Imagineers of War by Sharon Weinberger has a lot of context on his time in DARPA. Few things that I found particularly notable: * Licklider was conscious about not having too much fu
19.
by kelvich 4y ago
Postgres tracks maximal LSN among the evicted pages and passes it to the pageserver in the page request. If the pageserver hasn't received that LSN, it will wait for it to arrive.
20.
by kelvich 4y ago
Currently, we deploy three safekeepers, one in each AZ. We need to collect more stats on failure rates, and maybe we will go to 6 (3 AZs with two nodes in each) as Aurora does.
21.
by kelvich 4y ago
Right. Our design guideline is to get as much serverless behavior as possible while keeping full Postgres compatibility (in terms of features and expected performance). Single node Postgres can give you hundreds of thousands of small RW que
22.
by kelvich 4y ago
Good catch! Currently, we don't, and we rely on k8s to stop the old node. Technically speaking, if k8s and our control plane are always good at stopping the old primary, we don't need consensus at all. So that is more of a questio
23.
by kelvich 4y ago
The author is here, happy to answer questions if any.
24.
Paxos-based replication for Postgres(neon.tech)
8 points by kelvich 4y ago|0 comments
25.
PostgreSQL 14 Internals Book(postgrespro.com)
452 points by kelvich 4y ago|34 comments
26.
by kelvich 4y ago
It is about 3 seconds to start now, with about 1.5 seconds out of 3 being k8s time quant. So we hope to drive it below 1 second with some tweaks.
27.
by kelvich 4y ago
We are still experimenting with compute scaling, and the tech preview includes only a small fixed compute container. We have a custom proxy in front of a compute, and we can quickly change the underlying compute container with a bigger&#x2F
28.
by kelvich 4y ago
Our compute node is basically a usual postgres where we intercept WAL write and page read streams. In other words we don't do any compute sharding since we want to preserve vanilla postgres compatibility and any sharded solution will b
29.
by kelvich 4y ago
Now the most common setup is to copy the production database to the staging once in a while and test migration against staging. With branching, you can test each PR against its own production database branch -- just put branch creation in y
30.
by kelvich 4y ago
You can, no strings attached

More ›