Viewing profile — brasetvik

Atomic looks quite interesting, and the "wiki synthesis" is particularly interesting: I've been working on a suite of skills and a tiny MCP (also SQLite + SQLite-vec based) where t…

Also recommend this free book: https://postgrespro.com/community/books/internals

pganalyze's blog is a goldmine of Postgres tidbits, a lot of which is recapped in their YouTube channel: https://www.youtube.com/@pganalyze6516 I'm not at all affiliated, just a ha…

Or from the other perspective of the trade-off: One caveat with MSSQL is that ALL concurrent transactions must pay the overhead if _some_ transactions need serializable guarantees?…

A bit of birthday paradox too? :)

Nice job, eugene-khyst. Looks very comprehensive from an initial skim. I've worked on something in the same space, with a focus on reliable but flexible synchronization to many con…

This is also a pretty cool presentation on the topic: https://www.blackhat.com/docs/us-17/thursday/us-17-Tsai-A-Ne...

Some overlap, but my similar post mentions a few other things too, with a lot of links to sources to learn more :) https://medium.com/cognite/postgres-can-do-that-f221a8046e

Reading that thread it doesn't seem like the official image shipped with any cryptominer at any point, and that it's more likely that the container got compromised in other ways. (…

Advisory locks are purely in-memory locks, while row locks might ultimately hit disk. The memory space reserved for locks is finite, so if you were to have workers claim too many q…

It’s the wat I’ve seen have the most security impact. Deep merging two JSON parsed objects is innocuous enough everywhere else that most don’t think twice about doing it. Lots of w…

>> JSON.parse("{}")["__proto__"]["A"] = "T" "T" >> W = {} Object { } >> W.A "T"

I’d agree that ReDoS is a repeat offender in having overblown severity in vulnerability reports, and prototype pollution reports have contributed to a fair bit of noise when poppin…

I made a similar resource (and a talk) with different kinds of tips, that also has a lot of links to learning more about the different topics: https://medium.com/cognite/postgres-c…

I think Blender is worth an honerable mention. :) Geometry nodes, part of «everything Nodes», is pretty interesting: https://youtu.be/kMDB7c0ZiKA

It has long since been cleaned up, but the history of Lucene's Levenshtein automatons are a fascinating mix of pragmatism, hackery, grit, and engineering. Using a Python library to…

I don't know anything about their product, but their security team has been publishing high quality research, e.g. https://www.wiz.io/blog/the-cloud-has-an-isolation-problem-p... a…

It's not a single digit minute read, but to me "Git from the Bottom Up" was what really made me understand git a long time ago. https://jwiegley.github.io/git-from-the-bottom-up/ g…

> In this system, the client would request a range (start time, max count) of events via an HTTP request, and the response would include the "end time" that can be used in the next…

> Its was actually very surprising to me to find PG does not cache query plans but instead replans on every execution! If you used prepared statements, `plan_cache_mode` (since Pos…

Hadn't come across Braid yet. Looks interesting. Thanks for the link :)

> Though to address the GP a bit, the problem of concurrent writers without a sequencer (like a database) is less common than you might think. My point was that even if you have a …

It'd be great to get a fairly standard way of doing this. :) Having worked in this problem space a bit recently, I find this part a bit too optimistic: > The event.id is used as la…