Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1syC4P-00F0RX-Ux for pgsql-general@arkaria.postgresql.org; Tue, 08 Oct 2024 15:24:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1syC4O-009eRG-N8 for pgsql-general@arkaria.postgresql.org; Tue, 08 Oct 2024 15:24:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1syC4O-009eR7-67 for pgsql-general@lists.postgresql.org; Tue, 08 Oct 2024 15:24:16 +0000 Received: from mail-wr1-x436.google.com ([2a00:1450:4864:20::436]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1syC4L-003A8o-9f for pgsql-general@postgresql.org; Tue, 08 Oct 2024 15:24:14 +0000 Received: by mail-wr1-x436.google.com with SMTP id ffacd0b85a97d-37cd26c6dd1so5581520f8f.3 for ; Tue, 08 Oct 2024 08:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728401052; x=1729005852; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fK2Y24nsV8rz2pWG4ws34Y3z7mi5PKL/84Yth7eskhY=; b=kYEiII/uW4Yi2o8MoW/ei3pSoplOWgTVbSgvAAc8tlqqbR/aUrq+6YBk06gzvwiTTl fFDcE1tdCemma/KKoBh4lQ7vVT/QhNUdjX23+xO5alNTiPFzqZcuOrJqf6OJp5GJI3Pe nS6Hx+zi/HcNaLQW74+mRN7uzvl27L6xvXgFkTUghI3sHxvjMf/tbiZ864lr9u/MNkk+ FPfX9IYuHOuCbrdwIymo7OJk8MrvymyCKlBG+Y040nSQxza91+kVjHVSPdJzKO8LC0wm iidzWZkbYprgaVp+9i0V7AgWhVtx/1k6jM41LzyUvduYbhIpbBk+o0BICgMu/IJiXpn3 mywQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728401052; x=1729005852; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fK2Y24nsV8rz2pWG4ws34Y3z7mi5PKL/84Yth7eskhY=; b=r9Avg+9Gr2wK3Xw1IeryRNXmZ8mRf7KO8kq1y7jNaJaEUU/fYMQZ38pT5WMr/izAyO hO5T/HDqVOwxXvmtymyHZaDWu+WyXPkJLykMTivvUKbUgd++UWqcMce/dgwbxXHgAVds 9ehmCP2RxjnmGFtit0vi4RXCv/iMos3CPameUnPSNY20bH35EPrtII+8KwjcULVUrYbe oPgWIqtlzTvMf5HbyLeVxswS8XbeH9Vwaswycyhokafr1giuF3RdxvybBKvagzpQCJhp 0XsNzxSm6uZDNVaud1vS6IN35YGnW7WBAPxDbFbvAV/As5jj0jN9x8aW1oUqTnfXbKoS zrVA== X-Forwarded-Encrypted: i=1; AJvYcCUzcxwx7af+D2vEigku3jRr72HDH1q12KmLTBQnfWxVCBWWClc4JDm0LqhiVVG9/B1z6QaW6D9HyOpaVEXN@postgresql.org X-Gm-Message-State: AOJu0YxkwGsWdHsfrMaIoat18QUaPU+/d4yV1u9Wlr7fA9uxd+7xBrz9 xnOh3Hv/ZqBE0bWB8XCohA0vfMdzCIMF2gxIL6semautTdQvOq3pp9O/yuNRIVFtMq2MUqKORZK bKG1a8AHVSiEVqRAXGr85GOM3efo= X-Google-Smtp-Source: AGHT+IGLXZkdPi2VbGExAyKTY0N7t6Ejo4xESAyhDz5NBSVLF2LrFQDHhna2YQsaQ+7/UFG1D2yO2iWjX5CAbyesmG8= X-Received: by 2002:adf:f203:0:b0:37c:cd1d:b870 with SMTP id ffacd0b85a97d-37d0e765eb0mr13922346f8f.29.1728401051385; Tue, 08 Oct 2024 08:24:11 -0700 (PDT) MIME-Version: 1.0 References: <38f7cd4c-8586-4c34-9770-a70e083823a5@aklaver.com> <4a246d11-d250-414e-a7e6-1aeb6d1264aa@aklaver.com> <0a805069f207406b6c68a023bda5a9bbcda1db16.camel@gunduz.org> <3f24695a-3605-49d5-a833-fd6f45bb1fce@aklaver.com> In-Reply-To: <3f24695a-3605-49d5-a833-fd6f45bb1fce@aklaver.com> From: Paul Brindusa Date: Tue, 8 Oct 2024 16:23:59 +0100 Message-ID: Subject: Re: libpq5 error To: Adrian Klaver Cc: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= , pgsql-general Content-Type: multipart/alternative; boundary="000000000000b28c330623f8bad2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b28c330623f8bad2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi guys, I've just retried patching the host as we speak with no luck, I am getting the exact same thing. Following Devrim's guidance i've manually upgraded the repo file that came down via dnf and still getting the mismatch error: Error: Transaction test error: file /usr/share/pgsql/postgres.bki from install of libpq5-17.0-42PGDG.rhel9.x86_64 conflicts with file from package postgresql-server-15.8-1.module+el9.4.0+25512+c6b50a48.x86_64 file /usr/share/pgsql/system_constraints.sql from install of libpq5-17.0-42PGDG.rhel9.x86_64 conflicts with file from package postgresql-server-15.8-1.module+el9.4.0+25512+c6b50a48.x86_64 Any ideas? On Tue, Oct 8, 2024 at 4:06=E2=80=AFPM Adrian Klaver wrote: > On 10/8/24 01:01, Paul Brindusa wrote: > > Good morning Devrim, > > > > Is libpq5 an important component that needs the upgrade? > > From here: > > https://www.postgresql.org/docs/current/libpq.html > > "libpq is the C application programmer's interface to PostgreSQL. libpq > is a set of library functions that allow client programs to pass queries > to the PostgreSQL backend server and to receive the results of these > queries. > > libpq is also the underlying engine for several other PostgreSQL > application interfaces, including those written for C++, Perl, Python, > Tcl and ECPG. So some aspects of libpq's behavior will be important to > you if you use one of those packages. In particular, Section 32.15, > Section 32.16 and Section 32.19 describe behavior that is visible to the > user of any application that uses libpq." > > To me that is, yes it is important. > > > I am wanting to try after Adrian's suggestion yesterday to see if I can > > update the repo file first of all since it came with the rest of the > > updates. > > > > If that does not solve it, I would consider disabling the package. > > > > On Tue, Oct 8, 2024 at 8:48=E2=80=AFAM Devrim G=C3=BCnd=C3=BCz > > wrote: > > > > Hi, > > > > On Mon, 2024-10-07 at 08:44 -0700, Adrian Klaver wrote: > > > > Unknown Error occurred: Transaction test error:\n file > > > > /usr/share/pgsql/postgres.bki from install of > > > > libpq5-17.0-42PGDG.rhel9.x86_64 conflicts with file from packa= ge > > > > postgresql-server-15.8-1.module+el9.4.0+25512+c6b50a48.x86_64\= n > > file > > > > /usr/share/pgsql/system_constraints.sql from install of > > > > libpq5-17.0-42PGDG.rhel9.x86_64 conflicts with file from packa= ge > > > > postgresql-server-15.8-1.module+el9.4.0+25512+c6b50a48.x86_64\= n. > > > > Ah ok. So basically it means PostgreSQL is installed from Red Hat > > packages, not PGDG. I would suggest you either not to use PGDG repo= s > at > > all for consistency, or switch to PGDG repo and use our packages as= a > > whole. > > > > ...or you can edit /etc/yum.repos.d/pgdg-redhat-all.repo file, and > add > > > > exclude=3Dlibpq5 > > > > under the [pgdg-common] section so that dnf will ignore that. > > > > Regards, > > > > > > -- > > Devrim G=C3=BCnd=C3=BCz > > Open Source Solution Architect, PostgreSQL Major Contributor > > Twitter: @DevrimGunduz , @DevrimGunduzTR > > > > > > > > -- > > Kind Regards, > > Paul Brindusa > > paulbrindusa88@gmail.com > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --=20 Kind Regards, Paul Brindusa paulbrindusa88@gmail.com --000000000000b28c330623f8bad2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi guys,

I&= #39;ve just retried patching the host as we speak with no luck, I am gettin= g the exact same thing.
Following Devrim's guidance i've = manually upgraded the repo file that came down via dnf=C2=A0 and still gett= ing the mismatch error:


Error: Tran= saction test error:
=C2=A0 file /usr/share/pgsql/postgres.bki from insta= ll of libpq5-17.0-42PGDG.rhel9.x86_64 conflicts with file from package post= gresql-server-15.8-1.module+el9.4.0+25512+c6b50a48.x86_64
=C2=A0 file /u= sr/share/pgsql/system_constraints.sql from install of libpq5-17.0-42PGDG.rh= el9.x86_64 conflicts with file from package postgresql-server-15.8-1.module= +el9.4.0+25512+c6b50a48.x86_64

Any ideas?

On Tue, Oct 8, 2024 at 4:06=E2=80=AFPM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 10/8/24 01:01, Paul= Brindusa wrote:
>=C2=A0 =C2=A0Good morning Devrim,
>
> Is libpq5 an important component that needs the upgrade?

=C2=A0From here:

https://www.postgresql.org/docs/current/libpq.html=

"libpq is the C application programmer's interface to PostgreSQL. = libpq
is a set of library functions that allow client programs to pass queries to the PostgreSQL backend server and to receive the results of these
queries.

libpq is also the underlying engine for several other PostgreSQL
application interfaces, including those written for C++, Perl, Python,
Tcl and ECPG. So some aspects of libpq's behavior will be important to =
you if you use one of those packages. In particular, Section 32.15,
Section 32.16 and Section 32.19 describe behavior that is visible to the user of any application that uses libpq."

To me that is, yes it is important.

> I am wanting to try after Adrian's suggestion yesterday to see if = I can
> update the repo file first of all since it came with the rest of the <= br> > updates.
>
> If that does not solve it, I would consider disabling the package.
>
> On Tue, Oct 8, 2024 at 8:48=E2=80=AFAM Devrim G=C3=BCnd=C3=BCz <devrim@gunduz.org <= br> > <mailto:devr= im@gunduz.org>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0Hi,
>
>=C2=A0 =C2=A0 =C2=A0On Mon, 2024-10-07 at 08:44 -0700, Adrian Klaver wr= ote:
>=C2=A0 =C2=A0 =C2=A0 > > Unknown Error occurred: Transaction test= error:\n file
>=C2=A0 =C2=A0 =C2=A0 > > /usr/share/pgsql/postgres.bki from insta= ll of
>=C2=A0 =C2=A0 =C2=A0 > > libpq5-17.0-42PGDG.rhel9.x86_64 conflict= s with file from package
>=C2=A0 =C2=A0 =C2=A0 > > postgresql-server-15.8-1.module+el9.4.0+= 25512+c6b50a48.x86_64\n
>=C2=A0 =C2=A0 =C2=A0file
>=C2=A0 =C2=A0 =C2=A0 > > /usr/share/pgsql/system_constraints.sql = from install of
>=C2=A0 =C2=A0 =C2=A0 > > libpq5-17.0-42PGDG.rhel9.x86_64 conflict= s with file from package
>=C2=A0 =C2=A0 =C2=A0 > > postgresql-server-15.8-1.module+el9.4.0+= 25512+c6b50a48.x86_64\n.
>
>=C2=A0 =C2=A0 =C2=A0Ah ok. So basically it means PostgreSQL is installe= d from Red Hat
>=C2=A0 =C2=A0 =C2=A0packages, not PGDG. I would suggest you either not = to use PGDG repos at
>=C2=A0 =C2=A0 =C2=A0all for consistency, or switch to PGDG repo and use= our packages as a
>=C2=A0 =C2=A0 =C2=A0whole.
>
>=C2=A0 =C2=A0 =C2=A0...or you can edit /etc/yum.repos.d/pgdg-redhat-all= .repo file, and add
>
>=C2=A0 =C2=A0 =C2=A0exclude=3Dlibpq5
>
>=C2=A0 =C2=A0 =C2=A0under the [pgdg-common] section so that dnf will ig= nore that.
>
>=C2=A0 =C2=A0 =C2=A0Regards,
>
>
>=C2=A0 =C2=A0 =C2=A0--
>=C2=A0 =C2=A0 =C2=A0Devrim G=C3=BCnd=C3=BCz
>=C2=A0 =C2=A0 =C2=A0Open Source Solution Architect, PostgreSQL Major Co= ntributor
>=C2=A0 =C2=A0 =C2=A0Twitter: @DevrimGunduz , @DevrimGunduzTR
>
>
>
> --
> Kind Regards,
> Paul Brindusa
> paulbrin= dusa88@gmail.com <mailto:paulbrindusa88@gmail.com>

--
Adrian Klaver
adrian.klave= r@aklaver.com



--
Kind Regards,
Paul Brindusa
--000000000000b28c330623f8bad2--