Re: Vacuuming the operating system documentation
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Thomas Munro <thomas.munro@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-06-06T14:41:17Z
Lists: pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: > On 2020-06-06 06:57, Thomas Munro wrote: >> We're carrying a bunch of obsolete and in one case insecure advice on >> kernel settings. Here's an attempt to clean some of that up. > These changes seem sensible to me. +1 >> HP-UX: >> * Drop advice for v10. 11.x came out 23 years ago. > We still have a version 10 in the build farm. :) Yeah, but I don't need advice on installing PG on that ;-). In general, I think the filter rule could be: is it likely that someone would try to install PG 13-or-later from scratch (with no pre-existing installation) on this OS version? If there is a pre-existing install, they'll already have dealt with any kernel configuration issues. So I concur with dropping all this stuff, and while we're at it I'd vote for getting rid of the oom_adj para. RHEL6 will be fully EOL around the time PG13 comes out, so I don't believe anyone's making brand new installs there either. regards, tom lane
Commits
-
Doc: Update example symptom of systemd misconfiguration.
- 682c28baf925 10.14 landed
- a35896c4b2a1 11.9 landed
- b944b1d1a9ac 12.4 landed
- a1c940cc5882 13.0 landed
- d094bf93014b 14.0 landed
-
Doc: Clean up references to obsolete OS versions.
- c8be915aa9fc 13.0 landed