Re: postgresql 16

MFH stands for “merged from HEAD”, which is FreeBSD parlance for merging some changeset from the HEAD of some Git branch, most usually “main”, into some other branch, in this case one of the ports quarterly branches.

This applies to the conversation at hand because, as you may know, FreeBSD offers binary packages either from a “quarterly” repository, i.e.:

-> cat /etc/pkg/FreeBSD.conf 
(…)
FreeBSD: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

which is currently pulling from the ports tree’s 2024Q4 branch, or from a “latest” repository, which always builds directly from the tip of the ports tree’s main branch (hence the name). At the tip of the 2024Q4 branch the PostgreSQL ports are currently at 16.4, and the bump to 16.6 hasn’t been “MFH’d” into 2024Q4; that is why no amount of “pkg update && pkg upgrade” will ever show you any updates for those packages, at least not until an MFH occurs, if it does, or a new “quarterly” branch is cut, e.g. 2025Q1 (whenever that happens), and the upstream builders switch the “quarterly” repo to it.

As for how you’d install *only* the updated PostgreSQL packages from the latest repository, while keeping the rest of your system on quarterly, I guess that could be achieved by some combination of:

1. mkdir -pv /usr/local/etc/pkg/repos
2. echo 'FreeBSD: { url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest” }’ > /usr/local/etc/pkg/repos/FreeBSD.conf
3. pkg update -f
4. pkg upgrade postgresql16-server postgresql16-client (etc.)
5. (PostgreSQL’s usual db server update dance)
6. rm -f /usr/local/etc/pkg/repos/FreeBSD.conf
7. pkg update -f

But I’d be wary of the resulting mixture of packages possibly causing unforeseen and unnecessary problems. Caution is advised.

HTH!

> On Dec 3, 2024, at 5:32 PM, fatty.merchandise677@aceecat.org wrote:
> 
> On Tue, Dec 03, 2024 at 08:54:12AM +0100, Andrea Venturoli wrote:
> 
>> Maybe the OP is using 2024Q4 port tree?
> 
> Yes.
> 
> I don't really want any churn other than security fixes. Is there
> a way to use mostly Q4 but make an exception for a particular package
> or even just a particular update? I guess I'd be fine with just
> downloading the package with curl and unpacking it manually, in this
> once case.
> 
>> PostgreSQL updates are often not MFH (even for security fixes).
> 
> Sorry, please explain MFH. I'm a recent arrival ;-)
> 
> -- 
> Ian
>