I also don't think it has any indexes either? So search performance is a function of the number of entries.
24,412 karma · joined December 27, 2014
I also don't think it has any indexes either? So search performance is a function of the number of entries.
Does the GPL2 license here mean that anyone writing extensions for VillageSQL must license extensions as GPL2? If so that's still quite far from the Postgres ecosystem where plenty of companies are built largely around being proprietary extensions.
> Most online resources chalk this up to connection churn, citing fork rates and the pid-per-backend yada, yada. This is all true but in my opinion misses the forest from the trees. The real bottleneck is the single-threaded main loop in the postmaster. Every operation requiring postmaster involvement is pulling from a fixed pool, the size of a single CPU core. A rudimentary experiment shows that we can linearly increase connection throughput by adding additional postmasters on the same host.
Few distributed filesystems/object stores seem to use Raft (or consensus at all) for replicating data because it's unnecessary overhead. Chain replication is one popular way for replicating data (which uses consensus to manage membership but the data path is outside of consensus).
scattered-thoughts.net author is Jamie Brandon. :)
https://www.usenix.org/legacy/event/fast08/tech/full_papers/...
https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&d...
Ah ok I was missing this and this does sound like what I was expecting. Thank you!
Needing pip and virtualenvs was enough to make me realize uv wasn't what I was looking for. If I still need to manage virtualenvs and call pip I'm just going to do so with both of these directly.
I had been hoping someone would introduce the non-virtualenv package management solution that every single other language has where there's a dependency list and version requirements (including of the language itself) in a manifest file (go.mod, package.json, etc) and everything happens in the context of that directory alone without shell shenanigans.
At least personally when Jamie says something I listen. :)
[0] https://www.postgresql.org/docs/current/logical-replication-...
The page you link even mentions scenarios they know about that do happen and that they still assume won't happen. So even sqlite doesn't make anywhere near as strong a claim as you make.
> SQLite assumes that the operating system will buffer writes and that a write request will return before data has actually been stored in the mass storage device. SQLite further assumes that write operations will be reordered by the operating system. For this reason, SQLite does a "flush" or "fsync" operation at key points. SQLite assumes that the flush or fsync will not return until all pending write operations for the file that is being flushed have completed. We are told that the flush and fsync primitives are broken on some versions of Windows and Linux. This is unfortunate. It opens SQLite up to the possibility of database corruption following a power loss in the middle of a commit. However, there is nothing that SQLite can do to test for or remedy the situation. SQLite assumes that the operating system that it is running on works as advertised. If that is not quite the case, well then hopefully you will not lose power too often.
So I think people are really eager for high quality talks and chances to gather with smart people.
What's more I think there are not enough meetups in almost any major city to satisfy the demand of speakers or attendees. For example, NYC Systems gets hundreds of people asking to speak (we have 12 speakers a year) and gets 2-3x as many attendees wanting to come as we have space for.
https://transactional.blog/blog/2024-data-replication-design...