frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
1420•jasondavies•5h ago•653 comments

Inkling 2 Mini

https://thinkingmachines.ai/news/inkling-2-mini/
580•jasondavies•4h ago•94 comments

Levent Alpöge claims proof of the Generalized Riemann Hypothesis [pdf]

https://alpo.ge/remark.pdf
2301•iamronaldo•10h ago•1557 comments

NINLIVE: The Nine Inch Nails live archive

https://ninlive.com/
72•CharlesW•1h ago•17 comments

We promoted developers into architects without informing them

https://manidoraisamy.com/developer-to-architect.html
263•QueensGambit•6h ago•167 comments

Unforced Navier-Stokes Singularity and the Generalized Riemann Hypothesis

https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singu...
317•archon1410•7h ago•124 comments

Sir Brian May adds new dimension to Hera asteroid

https://www.esa.int/articles/about-us/directorates/operations/space-safety/hera/sir-brian-may-add...
17•mooreds•1h ago•0 comments

Language Models Can Rewrite Their Own Weights

https://arxiv.org/abs/2611.21885
324•lwhsiao•7h ago•106 comments

Re: Riemann

https://borretti.me/article/re-riemann
9•_dain_•39m ago•0 comments

Finite-time blow-up for the Navier–Stokes equations

https://github.com/tristanbuckmaster/navier-stokes/
252•trotro•8h ago•79 comments

DreamCoder: Coding harness and IDE from the author of Mastering Emacs

https://www.masteringemacs.org/article/announcing-dreamcoder
80•facundo_olano•4h ago•11 comments

And yet, it moves

https://signoregalilei.com/2026/11/20/and-yet-it-moves/
67•notfried•4h ago•30 comments

If you can't explain something in simple terms, you don't understand it (2017)

https://kottke.org/17/06/if-you-cant-explain-something-in-simple-terms-you-dont-understand-it
610•sammatilda•14h ago•288 comments

Vibecoding an inference chip

https://ankitg.me/blog/vibecoding-inference-chip/
103•ankitvgupta•6h ago•36 comments

The stochastic parrots have apparently proved the Riemann Hypothesis

https://scottaaronson.blog/?p=10344
194•stratos123•4h ago•158 comments

Winedroid – run Android apps without Android (WASM demo)

https://winedroid.soham.sh/demo/
88•sohzm•4h ago•25 comments

Frostbite: A new CPU architecture discovered, designed and verified by AI

https://architectlabs.com/blog/frostbite
615•shioyama•14h ago•320 comments

Signal Is Serious About Protecting Your Privacy

https://signal.org/blog/protecting-your-privacy/
488•dotcoma•14h ago•296 comments

Nvidia accounting under SEC investigation, sources say

https://finance.yahoo.com/markets/article/nvidia-stock-extends-25-trillion-rout-as-sec-probe-repo...
206•ftchd•4h ago•96 comments

Replacing implicit optionals with a None type in TypeDB

https://typedb.com/blog/replacing-implicit-optionals-with-a-none-type-in-typedb
6•flyingsilverfin•3d ago•0 comments

Show HN: OpenComputer – an open source alternative to Devin

https://github.com/diggerhq/opencomputer
50•iacguy•4h ago•15 comments

Nasdaq erases all 2026 gains

https://www.cnbc.com/2026/11/19/stock-market-today-live-updates.html
83•mv4•1h ago•33 comments

AI may have solved the most important problem in mathematics

https://www.economist.com/science-and-technology/2026/11/20/ai-may-have-solved-the-most-important...
9•vinni2•1h ago•3 comments

Show HN: An API for word timestamps from speech, 75% within 20ms

https://quebec.yarn.so
55•jasperstory•3d ago•8 comments

The Hungry Butler Effect: Concealed Commercial Incentives in LLMs

https://www.researchgate.net/publication/418143113_The_Hungry_Butler_Effect_Concealed_Commercial_...
9•undefinedmethod•2h ago•4 comments

I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA

92•proberts•7h ago•129 comments

Show HN: I made an audio-to-MIDI model 60x more efficient

https://kobi.music/research/dettato
227•hidude562•3d ago•48 comments

Microsoft announces Windows Server 2028 with hardened security

https://www.bleepingcomputer.com/news/microsoft/microsoft-announces-windows-server-2028-with-hard...
65•N19PEDL2•2d ago•75 comments

Google Workers Tell Their Employer Not to Punish Schools That Don't Want AI

https://www.motherjones.com/politics/2026/11/google-alphabet-union-school-ai-protest-gemini-worke...
250•cdrnsf•7h ago•190 comments

Help github just deleted me

https://nate.mecca1.net/posts/2026-11-20_help/
40•01nate•47m ago•20 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.