frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Pill to treat pancreatic cancer hailed as 'biggest breakthrough in decades'

https://www.theguardian.com/society/2026/nov/20/pill-pancreatic-cancer-breakthrough-daraxonrasib
583•rafaelc•1d ago•140 comments

Lean verification of the Riemann Hypothesis

https://leanprover-community.github.io/blog/posts/riemann-hypothesis/
822•g-b-r•10h ago•664 comments

Inkling-2-Mini in 5.4 GB Memory

https://github.com/ShinMegamiBoson/lookatmyquant
349•k__•7h ago•91 comments

Brazil's tax authority open-sources its tax calculator on GitHub under MIT

https://www.gov.br/receitafederal/pt-br/assuntos/noticias/2026/novembro/receita-federal-publica-p...
745•dvaplima•4d ago•239 comments

Detonating a pile of lead azide

https://www.science.org/content/blog-post/detonating-huge-pile-lead-azide-really
515•beginning_end•11h ago•345 comments

PcapAnalyzer – self-hosted pcap analyzer with 27 problem detectors

https://github.com/sebaandrada-cell/PcapAnalyzer
50•sebaandrada•3h ago•5 comments

Getting the mind to steer the body to steer you

https://notnottalmud.substack.com/p/getting-the-mind-to-steer-the-body
143•jger15•1d ago•52 comments

My monitor was cutting my download speed by 75%

https://blog.tymscar.com/posts/studiodisplayethernet/
482•soheilpro•14h ago•231 comments

Advice for the next 100 Rust GUIs

https://linebender.org/blog/next-100-guis/
78•raphlinus•4h ago•7 comments

PostgreSQL Extensions in Go

https://jespino.github.io/gopgext/
117•valyala•8h ago•20 comments

Pandex – Official European Law for AI Agents, over MCP

https://www.pandex.io
27•vasie•4h ago•4 comments

The Emergence of Inequality in the Czech Corded Ware Culture

https://www.jna.uni-kiel.de/index.php/jna/article/view/1560/1746
26•marojejian•4h ago•11 comments

Inkling 2 Mini

https://thinkingmachines.ai/news/inkling-2-mini/
1384•jasondavies•1d ago•280 comments

Tasklet (YC P26) Is Hiring Product and Agent Infra Engineers

https://tasklet.ai/careers
1•mayop100•4h ago

Windows has two settings that bring work back after restart, both off by default

https://www.makeuseof.com/windows-can-bring-your-work-back-after-restart/
34•surprisetalk•2d ago•31 comments

Upload2Shell (CVE-2026-125396)

https://pwn.ai/upload2shell
77•f311a•6h ago•29 comments

Tropical Rainforests Species may be surprisingly young

https://phys.org/news/2026-11-species-tropical-rainforests-young-emergence.html
40•PaulHoule•4d ago•18 comments

Show HN: Zero C# – C# without a runtime or GC

https://onurgumus.github.io/zero-csharp/index.html
126•reverseblade2•9h ago•96 comments

Bolt's Scooters Are Becoming Accessibility Sensors

https://geoawesome.com/bolt-scooters-accessibility-mapping-wheels4wheels/
31•chippy•4d ago•37 comments

Verification files for the Lean proof of the Riemann Hypothesis

https://math.mit.edu/~drew/grh/
92•Bluestein•9h ago•36 comments

Exponential Behavior in Magic: The Gathering

https://levineuwirth.org/essays/exponential-magic/
89•neuwirth•3d ago•62 comments

Shaping the Loops, Closing the Loops

https://revyl.com/blog/pattern-engineering/
3•based0x10•3d ago•2 comments

Sandwich Simulator

https://stulle.app/
6•subdomain•1h ago•0 comments

RCE in Gnupg

https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
231•gdgghhhhh•16h ago•93 comments

LLMs can read and write executables byte by byte from a hex dump

https://sgiannopoulos.github.io/blog/machine-code-programming/
190•fortran77•3d ago•123 comments

Why there are still no non-WebKit browsers on iOS

https://blog.mozilla.org/en/mozilla/internet-policy/apple-ios-browser-engine-rules/
481•lapcat•1d ago•269 comments

Ask HN: I have been unemployed for 2y. 15 years of experience, US. What to do?

609•LetThingsBeDiff•1d ago•679 comments

I'm quite pleased by the tech architecture of my art website

https://klauria.tech/klauria-art/
147•evakhoury•1d ago•33 comments

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
2389•jasondavies•1d ago•1160 comments

Context-Generic Programming v0.8.0 – Pluggable trait implementations for Rust

https://contextgeneric.dev/blog/v0.8.0-release/
19•maybevoid•3d ago•0 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.