frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Unauthenticated remote code execution in Nginx

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
800•speedping•5h ago•341 comments

Seven new models at scalable price-performance

https://microsoft.ai/news/microsoft-ignite-2026/
335•gmays•4h ago•219 comments

Inside Deutsche Bank

https://www.inside-db.com/
414•gyre007•5h ago•147 comments

DNS resolvers are the wrong place to fight piracy

https://techstackups.com/articles/quad9-leaves-france-dns-blocking/
491•ritzaco•7h ago•168 comments

AI agents ask better questions than KPMG accountants in audit trial

https://europeanbusinessmagazine.com/ai-agents-better-questions-kpmg/
201•Betelbuddy•5h ago•101 comments

DaisyRose-27B: 1,200-task RL took Qwen3.8 from 5.6% to 12% on Terminal-Bench 4.1

https://www.radixark.com/blog/daisyrose-27b
35•de_sty•1h ago•4 comments

Search Browser – Minimalist WebKit browser with Chrome extension support

https://searchbrowser.app/
21•rsaz•1h ago•8 comments

Genie 4 is now available

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/genie-4-now-available-p...
115•leumon•2h ago•92 comments

The Magic of Partial Evaluation

https://jimmyhmiller.com/magic-of-partial-evaluation
58•aray07•2h ago•6 comments

Advancing chip design with OpenAI models

https://openai.com/index/advancing-chip-design-with-our-models/
80•vighneshiyer•3h ago•40 comments

The Cambridge Dictionary has named ‘human’ as the Word of the Year 2026

https://www.cam.ac.uk/news/cambridge-dictionary-reveals-word-of-the-year-2026
192•DeepLogin•6h ago•145 comments

KVM: x86: Unconditionally reset MMU context when emulating INIT (CVE-2026-99312)

https://www.cve.org/CVERecord?id=CVE-2026-99312
150•Kozmik1•5h ago•98 comments

Show HN: Mastra Factory, the open-source software factory we use to build Mastra

57•codekarate•4h ago•17 comments

The First Revolver: How We Got from Blackbeard's Six Pistols to the Six-Shooter

https://americanhandgunner.com/handguns/revolvers/the-first-revolver/
32•bushwart•3d ago•9 comments

Show HN: ExitPath – Open-source ways out of Slack, Notion and Microsoft 365

https://exitpath-ruddy.vercel.app/
102•zerocool0101•5h ago•19 comments

Show HN: Take Voyager 1 apart, down to a single memory chip

https://rshekhar.com/voyager/
102•raj-shekhar•4h ago•24 comments

Show HN: Nobody blocks a keyboard – Rooted Android as a physical USB Deck

https://github.com/mr-anjaneyam/Emittr
36•mr-anjaneyam•2d ago•37 comments

CrossPoint Reader

https://crosspointreader.com
57•kristianpaul•3h ago•26 comments

F-22 Next-Generation micro–Data Transfer Cartridge (mDTC)

https://sam.gov/workspace/contract/opp/8948e8601e964c6aba9c801eee16b1be/view
122•birdboat00•5h ago•77 comments

The x86 CPU: From 4004 to 486

https://pikuma.com/blog/history-of-x86-4004-to-486
112•ibobev•6h ago•30 comments

Sexp Matrix

https://lisper.cc/ideas/entangle.html
9•todsacerdoti•1h ago•2 comments

When Free Software Isn't Free Enough

https://foss.life/notes/2026/free-software-isnt-free-enough/
22•hn_acker•2h ago•4 comments

Launch HN: Maritime (YC F26) – A managed cloud for production AI agents

29•ashriv•3h ago•25 comments

Evidence (YC S21) Is Hiring

https://www.ycombinator.com/companies/evidence/jobs/1xb9PpP-founding-gtm-lead
1•amcaskill•9h ago

A live service duress prototype

https://github.com/Ymsniper/vault-share
7•Ymsniper•3d ago•0 comments

A Primer on Fourier Series (2025)

https://arxiv.org/abs/2510.18203
85•teleforce•6h ago•22 comments

Energy-Based Reasoners: 385x more efficient inference

https://energy-based-reasoners.github.io/
284•frenchmajesty•11h ago•44 comments

How to Bypass Rust's Orphan Rule

https://edvong.com/bypass-orphan-rule/
4•todsacerdoti•45m ago•0 comments

Google Gemini's "Tasks" Personal Assistant Is Now Free

https://blog.google/innovation-and-ai/products/gemini-app/tasks-in-gemini-free-new-features/
7•hackeratrandom•47m ago•2 comments

Octopus, Gecko and Tortoise: the 3 scanners hunting your AI keys

https://tin.computer/blog/fake-ai-crawler-secrets-scanners
12•demegire•2h ago•1 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.