Re: [PATCH 0/1] sched: Restore PREEMPT_NONE as default - Andres Freund

Nobody sensible runs the latest kernel; nobody running PG in production should be afraid of setting a non-default at either boot time or as a sysctl. So this will, most likely, be another step in building a PG database server (turn off pre-emption if your kernel is 7.0 or later and PG is pre-whatever-version).

At worst it might become a permanent part of building a PG server and a FAQ... but if it affects one thing this badly, it will affect others.

If you're running in a docker container you share the host kernel. You might not have a choice.