On 11/12 06:01, Stuart Henderson wrote: > On 2026/11/12 18:49, Mark Patruck wrote: > > Update to databases/postgresql 18.7 released today fixing lots of > > high scored CVEs. > > > > Overview CVEs: > > https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/ > > > > Changelog: > > https://www.postgresql.org/docs/18/release-18-7.html#RELEASE-18-7-CHANGES > > > > > > I didn't spot any issues with databases/timescaledb and net/zabbix, > > but especially when coming from older versions pay attention to > > > > https://www.postgresql.org/docs/18/release-18-7.html#RELEASE-18-7-MIGRATION > > > I still have this in my tree from when we bumped the semaphore limits > in the kernel, maybe worth incorporating? (this was pre-8.0 so can just > be merged straight into -stable as well).
That makes sense to me, so I'll include this when committing. Best, Jeremy > > > Index: pkg/README-server > =================================================================== > RCS file: /cvs/ports/databases/postgresql/pkg/README-server,v > diff -u -p -r1.42 README-server > --- pkg/README-server 7 Aug 2026 08:49:05 -0000 1.42 > +++ pkg/README-server 12 Nov 2026 17:56:08 -0000 > @@ -56,20 +56,10 @@ Restart PostgreSQL to allow these change > > Tuning for busy servers > ======================= > -The default sizes in the GENERIC kernel for SysV semaphores are not > -large enough for PostgreSQL. Adding the following in /etc/sysctl.conf > -should allow PostgreSQL to start: > - > - kern.seminfo.semmni=256 > - kern.seminfo.semmns=2048 > - > -While you can start PostgreSQL with smaller limits, it's probably > -not wise unless you are very resource constrained. > - > -You may also want to tune the max_connections value in the > -postgresql.conf file to increase the number of connections to the > -backend. However, for busy servers with many connections, these > -limits may need to be increased further. > +You may want to tune the max_connections value in the postgresql.conf > +file to increase the number of connections to the backend. However, > +for busy servers with many connections, other limits may need to be > +increased to accommodate this. > > By default, the _postgresql user, and so the postmaster and backend > processes run in the login(1) class of "postgresql". On a busy server, > @@ -77,8 +67,21 @@ it may be advisable to tune resources, s > descriptors (used for network connections as well as files), possibly > more memory, etc. > > -The capability database file is located at /etc/login.conf.d/postgresql > +These can be changed by editing the capability database file located at > +/etc/login.conf.d/postgresql > > +The default sizes in the GENERIC kernel for SysV semaphores may also > +need increasing if a very high number of PostgreSQL processes are > +required, or if other applications on the system also require > +semaphores. Adding the following in /etc/sysctl.conf should be > +sufficient for nearly any PostgreSQL use: > + > + kern.seminfo.semmni=256 > + kern.seminfo.semmns=2048 > + > +To calculate minimal required values for your configuration, consult > +https://www.postgresql.org/docs/${V_MAJOR}/kernel-resources.html > + > Upgrade Howto (for a major upgrade) > =================================== > If you didn't install PostgreSQL by following this README,
