Date: Fri, 10 Apr 2020 07:57:31 -0500 From: Kyle Evans <kevans@freebsd.org> To: Palle Girgensohn <girgen@freebsd.org> Cc: ports-committers <ports-committers@freebsd.org>, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r517600 - in head/databases: postgresql10-server postgresql11-server postgresql12-server postgresql94-server postgresql95-server postgresql96-server Message-ID: <CACNAnaF%2BVLxhPxiM3Q6aypikqSEtt9ba8pNvT7m3n_Zct9gQuQ@mail.gmail.com> In-Reply-To: <201911141624.xAEGOjTf052640@repo.freebsd.org> References: <201911141624.xAEGOjTf052640@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 14, 2019 at 10:24 AM Palle Girgensohn <girgen@freebsd.org> wrote: > > Author: girgen > Date: Thu Nov 14 16:24:45 2019 > New Revision: 517600 > URL: https://svnweb.freebsd.org/changeset/ports/517600 > > Log: > Upgrade PostgreSQL > > The PostgreSQL Global Development Group has released an update to all > supported versions of our database system, including 12.1, 11.6, 10.11, > 9.6.16, 9.5.20, and 9.4.25. This release fixes over 50 bugs reported > over the last three months. > > PostgreSQL 9.4 will stop receiving fixes on February 13, 2020, which is > the next planned cumulative update release. We suggest that you make > plans to upgrade to a newer, supported version of PostgreSQL. Please see > our versioning policy for more information: > > This update also fixes over 50 bugs that were reported in the last > several months. Some of these issues affect only version 12, but may > also affect all supported versions. > > Specific change to the FreeBSD port: > Starting now, the default for TZDATA has changed to using the underlying OS' > time zone database instead of the one built in to PostgreSQL. This change is > made since PostgreSQL will not release a patch in the event where the time zone > database changes, whereas FreeBSD will. > Just a heads up- I guess it's maybe too late now, but this last change really should have had an associated UPDATING or something to that effect to go with it. The PostgreSQL-distributed set of zones doesn't match what FreeBSD distributes exactly and actively broke at least one users' config on upgrade[0]. This has since been worked around in base in a way that isn't all that spectacular and won't even hit releases where it's usable for people for at least another year, but we didn't seem to even warn folks outside of this small note in the commit message that they should be on the lookout. =-( Thanks, Kyle Evans [0] https://www.postgresql.org/message-id/12717.1573846407%40sss.pgh.pa.us
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaF%2BVLxhPxiM3Q6aypikqSEtt9ba8pNvT7m3n_Zct9gQuQ>