frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
83•PaulHoule•1h ago•64 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
133•burntsushi•2h ago•35 comments

The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life (2007)

https://masnick.com/posts/the-secret-thinkpad-powerbutton-code-to-bring-dead-laptops-back-to-life/
246•sammatilda•7h ago•96 comments

Show HN: Fakemetrics.com – "build in public" like a superstar

https://fakemetrics.com/
10•tigranbs•54m ago•0 comments

Michael Mann's 'Heat' Copyright Fight Turns on a Deal with Himself

https://copyrightlately.com/michael-mann-heat-copyright-termination/
21•speckx•1h ago•1 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
30•maufl•1h ago•10 comments

OpenAI: Strengthening the fight against online child sexual abuse

https://openai.com/index/strengthening-online-child-safety/
27•rossant•50m ago•27 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
47•geerlingguy•2h ago•17 comments

Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings

http://groundworkcollaborative.org/news/amazons-decoy-deals-groundwork-investigation-reveals-near...
599•DeepLogin•5h ago•370 comments

How to make almost anything

https://pub.cba.mit.edu/863.26/site/
747•o4c•13h ago•122 comments

Jolt – Clojure that speaks C

https://jolt-lang.net/
21•michaelsbradley•2h ago•1 comments

Universal XSS in uBlock Origin from website-driven element picker

https://iter.ca/post/ubo-uxss/
572•zaik•16h ago•163 comments

Just 400 US Data Centers Use More Electricity Than Michigan

https://www.wired.com/story/data-centers-use-more-electricity-than-michigan/
22•Betelbuddy•57m ago•18 comments

The Active Directory Era Is Finally Over

https://infisical.com/blog/active-directory-machine-identity
72•FinnLobsien•4h ago•46 comments

Smallest possible nopert polyhedra: the Septopert

https://github.com/tom7/noperts/blob/main/septopert.md
28•RebelPotato•2d ago•2 comments

Interpreting claims that a theorem is correct because it was checked in Lean

https://xenaproject.wordpress.com/2026/11/12/and-the-proof-is-checked-in-lean/
236•matt_d•11h ago•103 comments

OOS – an open operating system for the Rigol Scopes

https://www.eevblog.com/forum/testgear/oos-an-open-operating-system-for-the-rigol-scopes/
103•qwezxcrty•2d ago•32 comments

A 512 KiB binary message teaching chess without a shared language

https://artemlegotin.com/golden-board/
22•legotin•4h ago•3 comments

Qwen4-Max

https://qwen.ai/blog?id=qwen4-max
817•ilreb•16h ago•436 comments

Software is breaking down at a systemic level

https://www.breck-mckye.com/blog/2026/11/software-is-breaking-down-at-a-systemic-level/
77•zero_shift•45m ago•61 comments

Researchers track whole body movement with just a smartwatch

https://news.cornell.edu/stories/2026/11/researchers-track-whole-body-movement-just-smartwatch
171•PaulHoule•3d ago•60 comments

What's Next for Nvidia?

https://steveblank.com/2026/11/15/whats-next-for-nvidia/
428•zdw•19h ago•545 comments

Old Bitly links are being hijacked

https://ransomnews.com/burger-king-tweet-bitly-link-hijack-2026/
368•hspeiser•20h ago•192 comments

US Banks report outages in latest tech hiccup

https://nypost.com/2026/11/16/business/outages-hit-chase-bank-of-america-and-wells-fargo-customers/
8•ericzawo•9m ago•0 comments

Quxnet Is a Breath of Fresh Air

https://moddedbear.com/quxnet-is-a-breath-of-fresh-air/
9•surprisetalk•4d ago•4 comments

Winudf – DVD / BluRay driver for DOS, Windows 1.x – 3x / 95 / 98 / ME

https://github.com/ages2001/WINUDF
74•Oxodao•11h ago•11 comments

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

https://bruceroettgers.eu/blog/protomaps/
449•bcye•23h ago•81 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
235•aillia•18h ago•62 comments

Handwriting, as a Font

https://ductus.sorenblank.com
441•coinfused•23h ago•73 comments

Nvidia was in trouble before the Jensen Huang mess

https://www.wired.com/story/nvidia-was-already-in-trouble-before-the-jensen-huang-mess/
153•Brajeshwar•3h ago•143 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.