public inbox for [email protected]
help / color / mirror / Atom feedFrom: Aaron Pavely <[email protected]>
To: Christoph Berg <[email protected]>
To: Saif Hakim <[email protected]>
To: [email protected]
Subject: Re: libpq 11.10 / 11.11 are not propertly released for bionic
Date: Sun, 14 Feb 2021 20:53:44 -0600
Message-ID: <CAGs4muXkJEbyZHg=9Jf6GUthx6Zgo6=qWmoTWhoQaTPyH5Q_zA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAHcM7L13D4MAByVkMz35BKtfDQB2rTXP88hrFj5TLHfSm16F3w@mail.gmail.com>
<[email protected]>
On Sun, Feb 14, 2021 at 2:53 PM Christoph Berg <[email protected]> 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 — even after I
point out that the database cluster itself is using the most recent release
of libpq from the 'main' component.
Aaron
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: libpq 11.10 / 11.11 are not propertly released for bionic
In-Reply-To: <CAGs4muXkJEbyZHg=9Jf6GUthx6Zgo6=qWmoTWhoQaTPyH5Q_zA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox