From nobody Tue Dec 03 23:01:51 2024 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Y2x4D19Q1z5gvKc for ; Tue, 03 Dec 2024 23:02:04 +0000 (UTC) (envelope-from jmpalacios@gmail.com) Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y2x4C6YXjz54WR for ; Tue, 3 Dec 2024 23:02:03 +0000 (UTC) (envelope-from jmpalacios@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-x82a.google.com with SMTP id d75a77b69052e-46695478d03so54737711cf.1 for ; Tue, 03 Dec 2024 15:02:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733266923; x=1733871723; darn=freebsd.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=CNmGvzv94tKdfsDT8Jdlenqhrh3lNMdKQkZohgU3g2M=; b=XMos4srcLnzQDbIbMLoJKNZ4hIK9IqpDrISQH54xPjQGziF3vHHeImHQw0Ka4gyF67 XSXlo3GbTowLeJJtPdPTllcM5mLQ7h2Pw7FSKGOYldXkuvoE5+i4++Na+X1CA3o98WeA HpDu64kaCJV8J8A7G4OVNuWxH47tT1D/5Sv/4rcxz4k4tYlXq2VM0q7Jb4I/2luSWEnQ LAY9/of4tu5G2t25OIdFpYURdmMrb+gEzRzl6Dn2dCu7HvjTsl/0x+vB+hD9Rgqflg82 p0LxrXsDSpl0VKKMILT5WYosME1EjMZDdjHEufj1gubz4p5qFFshK29zQABu2HcJ/zb+ /Hdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733266923; x=1733871723; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=CNmGvzv94tKdfsDT8Jdlenqhrh3lNMdKQkZohgU3g2M=; b=a41Dx2SZUISqaFtf0CrSU6KXUTHNhpWhF6xXbWm95ohU6ZUjeshWCs58A3YrhlKvAa eDy/DulNYrH63qtPKo+n6N33eNc1EKKzb4pVPfeXBfF7aOm9m4fhQGPGc38rYSYdFbjD /EwHfsKMllNikaZyvfi/IJRlDBlH2IZ82CHWjQtGtViDYxmL7IQNvJhrTzTf3RELK6Zh 6NnlCIRp6aF5Ikc0XqK2ELpJ+JJZzDvr3Q8SbHs6UNeTA+HlccFYAve0kC6BHaYJq3Uh FKGtLJ1PaO6Ld8SV05xNmfgFrkClgR3Oj5F22rJg4kMKOlkXvBFOrFReF4OVewiJvygq jERQ== X-Gm-Message-State: AOJu0YwNissIXLhAxQGeaVMOgRp761d8m4URYMAW+Zi4dNf6NPZgMV2T QFBUfPlHJtXIBe8itmcVs4yEYVt7YnxJVAO/nimBEsecZElJ57U1 X-Gm-Gg: ASbGncsznYTwxjI9ePfC/GEBhbKsnCW50SQUV7Z0GnUWBG1lA4QzgwuLYNs7B4FPTvm p7hxQjMIH7C8J/2JBuFkzHqYauWFUeYEyK3w6RnExO1VNq3zdwbDDyiokQ44Nlu9/xkHXmmTXzD BsHKIt6wHwG9fRw9H/xNIGOfiq3XZ4ARZc5/TjDK07MlZr1TZlaYni1fwdBf98mdQg+urSq6yh3 ksXuH94Ol71wLi4v9pmaXMiVWZOZWIJ+C+ELw8yHMCow5LhiLhlVJawXr9tRZ7tkj3rZWQdVufi N0k= X-Google-Smtp-Source: AGHT+IE9b1eAQOsPBW9khRGK7kje+L4W/MAyJ/eeqSYX78rX+d60HBMMikafmExWEsH2yEVJR7YRPg== X-Received: by 2002:a05:622a:1308:b0:465:3a62:a8f9 with SMTP id d75a77b69052e-4670c73acc1mr78958781cf.50.1733266922897; Tue, 03 Dec 2024 15:02:02 -0800 (PST) Received: from smtpclient.apple ([2600:4041:7970:8b10:a4ca:d095:c359:221e]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-466c4054d0bsm66810601cf.3.2024.12.03.15.02.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Dec 2024 15:02:02 -0800 (PST) From: Juan Manuel Palacios Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_F841E360-B03F-4903-93DF-85520A2D7E58" List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\)) Subject: Re: postgresql 16 Date: Tue, 3 Dec 2024 18:01:51 -0500 In-Reply-To: Cc: questions@freebsd.org To: fatty.merchandise677@aceecat.org References: <6cKxpppDaTNpexhV@aceecat.org> <3bc92b40-205f-4da1-ab9c-d3ae5bb5ab1a@netfence.it> X-Mailer: Apple Mail (2.3826.200.121) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Y2x4C6YXjz54WR X-Spamd-Bar: ---- --Apple-Mail=_F841E360-B03F-4903-93DF-85520A2D7E58 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 MFH stands for =E2=80=9Cmerged from HEAD=E2=80=9D, which is FreeBSD = parlance for merging some changeset from the HEAD of some Git branch, = most usually =E2=80=9Cmain=E2=80=9D, 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 =E2=80=9Cquarterly=E2=80=9D = repository, i.e.: -> cat /etc/pkg/FreeBSD.conf=20 (=E2=80=A6) 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=E2=80=99s 2024Q4 branch, = or from a =E2=80=9Clatest=E2=80=9D repository, which always builds = directly from the tip of the ports tree=E2=80=99s 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=E2=80=99t been = =E2=80=9CMFH=E2=80=99d=E2=80=9D into 2024Q4; that is why no amount of = =E2=80=9Cpkg update && pkg upgrade=E2=80=9D will ever show you any = updates for those packages, at least not until an MFH occurs, if it = does, or a new =E2=80=9Cquarterly=E2=80=9D branch is cut, e.g. 2025Q1 = (whenever that happens), and the upstream builders switch the = =E2=80=9Cquarterly=E2=80=9D repo to it. As for how you=E2=80=99d 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=E2=80=9D= }=E2=80=99 > /usr/local/etc/pkg/repos/FreeBSD.conf 3. pkg update -f 4. pkg upgrade postgresql16-server postgresql16-client (etc.) 5. (PostgreSQL=E2=80=99s usual db server update dance) 6. rm -f /usr/local/etc/pkg/repos/FreeBSD.conf 7. pkg update -f But I=E2=80=99d 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=E2=80=AFPM, fatty.merchandise677@aceecat.org = wrote: >=20 > On Tue, Dec 03, 2024 at 08:54:12AM +0100, Andrea Venturoli wrote: >=20 >> Maybe the OP is using 2024Q4 port tree? >=20 > Yes. >=20 > 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. >=20 >> PostgreSQL updates are often not MFH (even for security fixes). >=20 > Sorry, please explain MFH. I'm a recent arrival ;-) >=20 > --=20 > Ian >=20 --Apple-Mail=_F841E360-B03F-4903-93DF-85520A2D7E58 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 MFH stands for = =E2=80=9Cmerged from HEAD=E2=80=9D, which is FreeBSD parlance for = merging some changeset from the HEAD of some Git branch, most usually = =E2=80=9Cmain=E2=80=9D, 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 =E2=80=9Cquarterly=E2=80=9D repository, = i.e.:

-> cat = /etc/pkg/FreeBSD.conf 
(=E2=80=A6)
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=E2=80=99s 2024Q4 branch, or from a =E2=80=9Clatest=E2=80=9D= repository, which always builds directly from the tip of the ports = tree=E2=80=99s 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=E2=80=99t been = =E2=80=9CMFH=E2=80=99d=E2=80=9D into 2024Q4; that is why no amount of = =E2=80=9Cpkg update && pkg upgrade=E2=80=9D will ever show you = any updates for those packages, at least not until an MFH occurs, if it = does, or a new =E2=80=9Cquarterly=E2=80=9D branch is cut, e.g. 2025Q1 = (whenever that happens), and the upstream builders switch the = =E2=80=9Cquarterly=E2=80=9D repo to = it.

As for how you=E2=80=99d = 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=E2=80=9D }=E2=80=99 > = /usr/local/etc/pkg/repos/FreeBSD.conf
3. pkg update = -f
4. pkg upgrade postgresql16-server postgresql16-client (etc.)
5. = (PostgreSQL=E2=80=99s usual db server update = dance)
6. rm -f /usr/local/etc/pkg/repos/FreeBSD.conf
7. pkg = update -f

But I=E2=80=99d 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=E2=80=AFPM, = 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


= --Apple-Mail=_F841E360-B03F-4903-93DF-85520A2D7E58--