frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Universal XSS in uBlock Origin from website-driven element picker

https://iter.ca/post/ubo-uxss/
232•zaik•4h ago•56 comments

Qwen4-Max

https://qwen.ai/blog?id=qwen4-max
319•ilreb•4h ago•107 comments

Old Bitly links are being hijacked

https://ransomnews.com/burger-king-tweet-bitly-link-hijack-2026/
240•hspeiser•8h ago•126 comments

What's Next for Nvidia?

https://steveblank.com/2026/11/15/whats-next-for-nvidia/
179•zdw•6h ago•230 comments

How to Make Almost Anything

https://pub.cba.mit.edu/863.26/site/
6•o4c•24m ago•0 comments

Tor Project Issues Rapid-Response DoS-Defense Fix Amid Sustained DDoS Attack

https://forum.torproject.org/t/security-release-0-4-9-17/22454
104•aillia•5h ago•24 comments

Preserving 30 years of Salon journalism

https://blog.archive.org/2026/11/12/preserving-30-years-of-salon-journalism/
128•CharlesW•7h ago•37 comments

Protomaps: Self-hosting map tiles has gotten cheap and easy

https://bruceroettgers.eu/blog/protomaps/
262•bcye•10h ago•51 comments

The Miracle Cure: In 1977, a drug rejected by doctors became a sensation

https://slate.com/technology/2026/11/doctor-medicine-cancer-cure-pill-history.html
29•mutexjp•2d ago•15 comments

A short explainer on how El Niño works [video]

https://www.youtube.com/watch?v=7_JF3etiAv8
213•nharada•11h ago•92 comments

Handwriting, as a Font

https://ductus.sorenblank.com
212•coinfused•10h ago•44 comments

Stop Filming in Log

https://digitalfilms.wordpress.com/2026/11/15/stop-filming-in-log/
15•dabinat•1h ago•6 comments

Do we still have to denormalize? Have your schema and search it too

https://www.paradedb.com/blog/joins
50•philippemnoel•2d ago•6 comments

The MacBook Pro's OLED PWM problem

https://macanorak.com/the-macbook-pros-oled-pwm-problem-when-a-better-display-becomes-worse-to-use/
453•MacAnorak•16h ago•256 comments

Crows make decisions faster than we can

https://www.nytimes.com/2026/11/15/science/birdbrain-crows-birds-research-decision.html
208•gumby•12h ago•145 comments

Claude Code and Codex reverse engineered my 1994 Jeep's ECU over a $3 Arduino [video]

https://www.youtube.com/watch?v=WPj3aQ-xxpI
397•envoked•4d ago•196 comments

Tell HN: HN is being scraped for emails to scam

60•eks391•3h ago•12 comments

WebGL Flight Simulator with seed generated terrain

https://baron.by.dai.studio/
113•ranger_danger•9h ago•22 comments

Mini.nvim Is Now on Tangled

https://tangled.org/nvim-mini.org/mini.nvim
51•nerdypepper•6h ago•14 comments

Simple 8085 Computer

https://www.hackster.io/mit41301/simple-8085-computer-9fe156
14•AlexeyBrin•3d ago•1 comments

Coles hit by a cybersecurity incident

https://www.colesgroup.com.au/updates/
83•sagunsh•5h ago•60 comments

Debian Becomes Unresponsive after 6.1.0-55 Kernel Update

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1154101
28•artooro•1h ago•0 comments

Things That Turbo Pascal Is Smaller Than (2011)

https://prog21.dadgum.com/116.html
219•ksec•16h ago•116 comments

Skydio's asymmetrical F10 Lightrunner solves a problem with fixed-wing drones

https://spectrum.ieee.org/skydio-f10-lightrunner-asymmetrical-drone
25•Gaishan•6h ago•1 comments

Artificial Intelligence for the Z80

https://www.dfsantos.com/en/libro-ia-z80
18•AlexeyBrin•2d ago•2 comments

Microsoft 365 outage leads to chlorine gas poisoning of 15 hotel guests

https://www1.wdr.de/nrw/rheinland/rhein-erft-kreis/technischer-defekt-chlor-phantasialand-100.html
474•DeepLogin•11h ago•202 comments

A quest to create the perfect whiskey glass

https://www.nytimes.com/2026/11/13/dining/drinks/kurt-josef-zalto-whiskey-glass.html
60•Kaibeezy•2d ago•60 comments

1900s How do you Wash a Kimono?

https://www.oldphotosjapan.com/photos/877/laundry-washing-clothes-meiji-19th-century-vintage-albu...
42•Matrixik•2d ago•10 comments

Eclipse Mosquitto – An open source MQTT broker

https://github.com/eclipse-mosquitto/mosquitto
83•gregsadetsky•11h ago•30 comments

Clice v1.0 Released: Welcome to Modern C++

https://ykiko.me/en/articles/2105384023094834022/
126•molenzwiebel•12h ago•76 comments
Open in hackernews

Pglocks.org

https://pglocks.org/
80•hnasr•1y ago

Comments

whilenot-dev•1y ago
I'm a bit lost here.

Locking is a challenging problem in complex systems. Is this list to be interpreted as a "TODO: get rid of locking conflicts in future releases" or more a "NOTE: be aware there are known conflicts that will not change - find ways to work around them"?

EDIT: Also, is the creation of this list an automated or a manual effort?

tux3•1y ago
I think this is intended as educational material, not a list of things to fix.

The locks are here by necessity, it is not so easy at all to get rid of them. And even in special cases where it is possible, the complexity you have to introduce is not to be taken lightly...

If even a tenth of these disapppeared, it would be incredible, in a very surprising way.

atombender•1y ago
The creator looks like a developer and teacher, not a Postgres core team member. So I assume this is for documentation purposes.

I actually like this a lot, as there isn't a single place in the Postgres documentation that lists all the possible locks; it's spread out all over. Having a quick reference for what kinds of commands you'd be blocking with your transaction is valuable.

It's pretty evident that the pages have been programmatically generated, but I'd love know what it's generated from. I think you can derive this information from the documentation, but not sure if you can do it in an automated way without an LLM.

braiamp•1y ago
> there isn't a single place in the Postgres documentation that lists all the possible locks

Did you read this page? https://www.postgresql.org/docs/current/explicit-locking.htm...

atombender•1y ago
That's a great page, but it has several issues.

First, it isn't complete; as I said, the locking behaviour is spread out all over the Postgres documentation. For example, that page doesn't list what locks DROP INDEX takes. To find that out, you have to go to the documentation page for that command and read it carefully. In fact, really carefully — the locking behaviour is only documented under the section about CONCURRENTLY.

The page also doesn't list what possible commands are then blocked. Locks interact in subtle (and incorrectly named!) ways that are explained in the tables on that page ("Conflicting lock modes"), so to understand if something will block something else you have to look at the two commands you are curious about and then look at how their locks interact.

gulcin_xata•1y ago
I agree, it is not so straightforward to find out.
braiamp•1y ago
These are database locks, which means that depending which arrives first, the later transaction has to wait till the first one finishes to complete. These locks are about SQL commands and which commands can run concurrently with the others. There's a graph here of how that looks like https://pankrat.github.io/2015/django-migrations-without-dow...

Usually for maximum performance (minimum latency, maximum throughput) you want to have operations not lock each other, unless absolutely necessary, in which case you want them to be short.

whilenot-dev•1y ago
You make it sound like the conflict is just affecting performance and won't result in a deadlock. So it's for performance aware postgres clients/users, and not for postgres developers?
andyferris•1y ago
It is a guide for developers using postgres as a client, who need to write systems that don't deadlock, are performant and are correct. These are the (rather sharp) tools that postgres provides for doing so (or else you can use e.g. serializable isolation and optimistic concurrency, but in my experience that has too many false positives and bail out rather eagerly, whereas these tools let you be very precise and granular).
mebcitto•1y ago
Other relevant talks/blogs that I found really useful for understanding Postgres locks are:

* Unlocking the Postgres Lock Manager by Bruce Momjian: https://momjian.us/main/writings/pgsql/locking.pdf

* Anatomy of table-level locks by Gulcin Yildirim Jelinek: https://xata.io/blog/anatomy-of-locks

pasxizeis•1y ago
Shameless plug: I wrote a tool[1] that executes a given migration against a test database (e.g. in your CI) and reports back what locks it acquired.

The rationale being to have a "lock diagnostics report" commented in your PR's migration file.

It's a prototype and has a few rough edges and missing functionality, but feedback is more than welcome.

[1] https://github.com/agis/pglockanalyze

jononor•1y ago
Very practical! Locking is one of the things that can really bite when doing migrations.