"
pkg_add: Installed package `postgresql14-client-14.23' conflicts with `postgresql1[0-35-9]-client-[0-9]*' when trying to install `postgresql16-client-16.14'.
"

Wait. What?

#pkgsrc

@jspath55 Wow. Never seen that before, ... and can't reproduce it here :( (NetBSD aarch64 11.99.6, pkg_admin 20260227):

> pkg_admin pmatch 'postgresql1[0-35-9]-client-[0-9]*' 'postgresql14-client-14.23' && echo match
>

What version of the pkg_install tools do you have?

#pkgsrc

@agc Can't find a version numbers, but late 2024?

-r-xr-xr-x 1 root wheel 117568 Dec 16 2024 /usr/sbin/pkg_admin

I have an issue with PGSQL versions conflicting with #QGIS installs, where it seems to only like version 16. Long story, starting with testing QGIS 4 from pkgsrc work in progress.

Most likely a local glitch. :/

Edit:

For:
$ pkgin show-deps "qgis" | grep -i client

I get:
postgresql16-client>=16.0nb1

(implying v14 won't work, but 16, 17, *or* 18 *should* be okay.)

@agc Digging deeper, I found where #PostgreSQL versions are configured for #pkgsrc builds:

../../mk/pgsql.buildlink3.mk

PGSQL_VERSION_DEFAULT?= 16
PGSQL_VERSIONS_ACCEPTED?= 18 17 16 15 14 13

That clears up the "Use the 16, Luke" mystery. I'll check if 13 is off the table as there is no client now.

$ pkgin se "postgresql1[3-9]-client"
postgresql14-client-14.23 = PostgreSQL database client programs
... 15 16 17 ...
postgresql18-client-18.4 PostgreSQL database client programs