News for hackers. Stuff that matters.

rastignack

Yes for this particular use case it might help (no per-application aggregated temp file limit though). Also my grid workloads generate thousands of threads running queries with lots of small updates (job queues, calculation results..). I wish there was a way for postgresql to isolate those connections to a limited set of cores (or number of cores).

To avoid completely saturating the server.

Right now we advise using s3 and storing results in files, and asynchronously loading them with batch processes.

Interesting. It would need some work to handle all the workloads I’ve faced where you have two applications with different priorities (ie oltp or grid workloads and analytics). In those cases you want to make sure that BI users do not interrupt the transaction processing by assigning them a set of cores, a priority, and work mem limits for example. Looks doable without major changes.
I would be interested about a more detailed architecture overview of the io scheduler (like this: https://www.scylladb.com/2021/04/06/scyllas-new-io-scheduler...) and the thread scheduler.

PostgreSQL has historically been bad at managing the noisy neighbor problem, but with thread pools, and io priorities, it can be solved.

Has this been tackled here ?

Re:Why we built yet another Postgres connection pooler on Wednesday July 08, 2026 @07:24AM (#48830519)
And why it should be done upstream with a thread pool model and an internal scheduler as MS SQL server does.
Re:Ten years of ClickHouse in open source on Saturday June 20, 2026 @05:29AM (#48607767)
The thing is you are going to be comoditized on this too. And it’s going to be faster to migrate off your database with AI. You are going to need to have a plan.
I hope it could be used in the future to export pg_dump formated exports to s3.

One would be able to trigger maintenance jobs via simple lambda functions whose duration is capped.

Re:Zig: Build System Reworked on Sunday May 31, 2026 @05:18AM (#48344207)
And if you write to a bytes buffer?
Just monitor it and you’re done. I’ve delivered and maintained hundreds of pg instances and never faced this issue. There is so much literature about it that at some point no one even slightly skilled will face it.
Re:Kubernetes Ingress Nginx is retiring on Friday November 14, 2025 @01:31AM (#45924449)
I have tens of clusters to maintain. Quite an advertisement for ECS!
Re:Benchmarking Postgres 17 vs. 18 on Friday October 24, 2025 @02:59AM (#45691686)
Is there now a way to avoid double buffering and use direct IO in postgresql ?

Has anybody seriously benchmarked this ?

I don’t think io uring would make a difference with this setting but I’m curious, as it’s the default for oracle and sybase.

Re:Charlie Kirk shot at event in Utah on Wednesday September 10, 2025 @04:54PM (#45203525)
Remember to turn off autoplay on Twitter.
Re:Bcachefs Goes to "Externally Maintained" on Sunday August 31, 2025 @10:18AM (#45083324)
How about acknowledging you’ve been too sharp with words, apologizing, and attempting to move forward ?

I know other people in the kernel do the same mistake as you frequently do on mailing lists. But two wrongs do not make a right.

Re:Bcachefs to be removed from mainline Linux kernel on Wednesday August 13, 2025 @02:16PM (#44891920)
Some distributions do release hotfixes before they reach mainline kernel. If you expect end users to compile Linus’ kernel head, why couldn’t they compile your branch though ? They get timely fixes.
Re:Bcachefs to be removed from mainline Linux kernel on Wednesday August 13, 2025 @12:04PM (#44890251)
Maybe then you should have considered this file system as truly experimental and expected your end users to make frequent backups. And advertise it as such. You could also have some kind of dkms bleeding edge module for your users to test fixes before they reach the kernel.

This way you wouldn’t be so preoccupied about getting code as fast as possible in the kernel.

Re:Bcachefs to be removed from mainline Linux kernel on Wednesday August 13, 2025 @11:06AM (#44889440)
Maybe the FS was upstreamed too soon, causing your development velocity and the high expectations you have for your end users to be at odd with the well entrenched workflows of Linux maintainers.

In any case as a Linux user, I want to thank you for your work and for your code which taught me a lot.

I hope it didn’t take too much of a toll on you.

Let’s hope that with the recent stabilization, the maintenance will be easier.

Re:Bcachefs to be removed from mainline Linux kernel on Tuesday August 12, 2025 @01:55AM (#44872873)
Mr Torvalds has already said “we’re done”.

And Mr Overstreet’s behavior is still unprofessional.

I think this thread is really insightful to teach highly skilled individuals that people skills are as important as technical proficiency.

I have been this arrogant and abrasive dev. It’s bad and learning how to behave, mainly through parenting, was a net positive for my career.

People, please read and learn from this thread.

One does not justify a wrong by another wrong. It’s a classic sophism.

I do not live in the US but did see some truly shocking and illegal behaviors at gay prides and drag themed events.

So I’m just waiting to get more information.

So my point is to trust the law. I don’t see how controversial it can be.

“ sexualized adult performers wore revealing attire and burlesque outfits while interacting with the children”

I don’t think that’s healthy and I would wait for the trial to say anything more about that.

Re:I've returned to Linux but I miss PowerShell on Sunday July 27, 2025 @06:21AM (#44700230)
Nowadays a lot of people script in python
Re:Zig's New Async I/O on Sunday July 20, 2025 @03:04AM (#44622649)
I’ll finish it this summer, hopefully.
I don’t think channels and goroutines suck. For example their usage in golang’s ssh server implementation is eminently readable.

And performant enough.

Engineers ship with them, and do not care if there’s a purer system elsewhere.

Re:Zig's New Async I/O on Sunday July 13, 2025 @10:59AM (#44550893)
I wrote a simple ssh server in zig to learn the language in my spare time.

The new design makes the event loop / io much easier to reason about. Thanks Andy

Re:OpenTelemetry for Go: Measuring overhead costs on Monday June 16, 2025 @04:17PM (#44293030)
Would the sync.Pool trick mentionned here: https://hypermode.com/blog/introducing-ristretto-high-perf-g... help ? It’s lossy but might be a good compromise.
Re:Green Tea Garbage Collector on Sunday June 15, 2025 @06:46AM (#44281616)
Austin Clements at it again…
Re:Rustls Server-Side Performance on Saturday May 17, 2025 @04:00AM (#44012793)
In rust with some C code, ok. How is the DER format parsed for example ?

Regarding crypto operations, I know as of now for rust projects assembly is a must to have constant time guarantees.

Maybe there could be a way with intrinsics and a constant-time marker, similar to unsafe, to use pure rust.

In the meantime I think there still is too much C code.

It’s a great step in the good direction by the way.

Re:Rustls Server-Side Performance on Saturday May 17, 2025 @03:34AM (#44012691)
Is not rustls a mix of c++, assembly and rust ?

I think it’s not a good indication of the success of the language.

Re:Migrating to Postgres on Thursday May 15, 2025 @09:43AM (#43995017)
At $WORK, we are within the range of 2 billion rows per day on one of our apps. We do have beefy hardware and ultra fast SSD storage though.
Re:Redis is open source again on Friday May 02, 2025 @01:50AM (#43866564)
It’s not about religion. PostgreSQL devs do make money right ? Despite RDS.

Older »