MIME-Version: 1.0
References: 
 <CAHcM7L13D4MAByVkMz35BKtfDQB2rTXP88hrFj5TLHfSm16F3w@mail.gmail.com>
 <YCmN13P0W7PBFaVv@msg.df7cb.de>
In-Reply-To: <YCmN13P0W7PBFaVv@msg.df7cb.de>
From: Aaron Pavely <aaron@pavely.net>
Date: Sun, 14 Feb 2021 20:53:44 -0600
Message-ID: 
 <CAGs4muXkJEbyZHg=9Jf6GUthx6Zgo6=qWmoTWhoQaTPyH5Q_zA@mail.gmail.com>
Subject: Re: libpq 11.10 / 11.11 are not propertly released for bionic
To: Christoph Berg <myon@debian.org>, Saif Hakim <saif@benchling.com>,
 pgsql-pkg-debian@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b675f905bb571891"
Precedence: bulk

--000000000000b675f905bb571891
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Feb 14, 2021 at 2:53 PM Christoph Berg <myon@debian.org> wrote:

> That said, you shouldn't worry about libpq5 11 - using the 13 version
> from the "main" repository component is the recommended way. I guess
> the fact that no one has spotted that problem before means no one is
> actually using the "11" and the other versioned components.
>

Actually, I received a few complaints the other day from developers for the
bionic-pgdg/9.6 component when 9.6.21 was pushed, so Saif's issue was not
an isolated incident. At the time, I saw that the 'Packages' file was
similarly last updated in November. Everything looks good now, though.

While I recommend to my teams use the 'main' component for libpq, there
continues to be fear among many that libpq versions mismatched from the
parent database cluster version may cause unexpected issues =E2=80=94 even =
after I
point out that the database cluster itself is using the most recent release
of libpq from the 'main' component.

Aaron

--000000000000b675f905bb571891
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, Feb 14, 2021 at 2:53 PM Christoph=
 Berg &lt;<a href=3D"mailto:myon@debian.org">myon@debian.org</a>&gt; wrote:=
<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">That said, you shouldn&#39;t worry about libpq5 11 - using the =
13 version<br>
from the &quot;main&quot; repository component is the recommended way. I gu=
ess<br>
the fact that no one has spotted that problem before means no one is<br>
actually using the &quot;11&quot; and the other versioned components.<br></=
blockquote><div>=C2=A0</div><div>Actually, I received a few complaints=C2=
=A0the other day from developers for the bionic-pgdg/9.6 component when 9.6=
.21 was pushed, so Saif&#39;s issue was not an isolated incident. At the ti=
me, I saw that the &#39;Packages&#39; file was similarly last updated in No=
vember. Everything looks good now, though.</div><div><br></div><div>While I=
 recommend to my teams use the &#39;main&#39; component for libpq, there co=
ntinues to be fear among many that libpq versions mismatched from the paren=
t database cluster version may cause unexpected issues =E2=80=94 even after=
 I point out that the database cluster itself is using the most recent rele=
ase of libpq from the &#39;main&#39; component.</div><div><br></div><div>Aa=
ron</div></div></div>

--000000000000b675f905bb571891--