Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lBZEq-0003aY-VZ for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 15 Feb 2021 08:28:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lBZEp-0006gj-Sa for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 15 Feb 2021 08:28:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lBQM2-0007f9-AT for pgsql-pkg-debian@lists.postgresql.org; Sun, 14 Feb 2021 22:59:02 +0000 Received: from mail-yb1-xb2a.google.com ([2607:f8b0:4864:20::b2a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lBQLz-0007Wp-DD for pgsql-pkg-debian@postgresql.org; Sun, 14 Feb 2021 22:59:01 +0000 Received: by mail-yb1-xb2a.google.com with SMTP id m188so5367288yba.13 for ; Sun, 14 Feb 2021 14:58:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benchling.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=kyHr3h8MQbq6F11Anexb/x/Rw2zDcvMAxdKL0CbmRD4=; b=jvW58nqYbyFTbqLzQHxZaAdd1+TFfgYVHOdXDvOJiwBn2DnMAo0BVn921eX2bem5Ga GoJk8mW79MLAWuvD1ntumxUfiL7lR1clPZE/nuQyjnPanb2WlPUwaiPq/uTJnfdH/VBw 0z0ztzZn2S1ss40D9M8VUboy/ZJadkK490UZM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=kyHr3h8MQbq6F11Anexb/x/Rw2zDcvMAxdKL0CbmRD4=; b=QQO/7pX5ThpfYbMq5HAo7tiKdkvBu0DLN2gv6k/q0EVe1AH18OxPDSFaBfIrTOzaLp CzGNiSv5fZQQgczz7Er8l6pGTM7shgGaPAOlkV1J4cnO1ceuUlg6N2lQCrSSiPMO/t65 XxeeFAd8HAN6oPaZDSSAII+Bl0DGV26S2JV6xiWTms7/SzAWLWZTu0NDkPwr52ZUmRob 7BfFdsHOJoTqjz0WwEAZe9/kDNu4dcyTLL9MaQOppRUsjKC3sszq5BTySXt6MVlZVkwF aEABIOHFr4UWv9bC+nj2Um0FgZtKYfFX+V/2pfloYn43RS6KIe+dSkr5cUVtVwScPegX RBEw== X-Gm-Message-State: AOAM532el5r62lfDwoZtAYBuw2mHwRaRaizYbbcGayMYFGD68hwd5IPr jEAZMacE9nIN0/JIHnml3LSi6kcYBvc7JWWuBc8wWQ== X-Google-Smtp-Source: ABdhPJxQ7H7rmWcLC4D9wVBZ8pAc0Evwan8cL8zOVLbl9LVeh+Bk5V/UprmGYbEzvwxLqv8X0PoX9qVOqXQDIWAvxCc= X-Received: by 2002:a25:ad67:: with SMTP id l39mr19683165ybe.172.1613343537227; Sun, 14 Feb 2021 14:58:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Saif Hakim Date: Sun, 14 Feb 2021 14:58:46 -0800 Message-ID: Subject: Re: libpq 11.10 / 11.11 are not propertly released for bionic To: Christoph Berg , Saif Hakim , pgsql-pkg-debian@postgresql.org Content-Type: multipart/alternative; boundary="00000000000070012e05bb53d013" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000070012e05bb53d013 Content-Type: text/plain; charset="UTF-8" Hi Christoph, > that is indeed stale, thanks for spotting that. The problem is present > in the other distributions as well. I have now manually updated > bionic-pgdg, but I will leave the other untouched until I can figure Thanks!, I've confirmed that my repro no longer works and version 11 is installed. > That said, you shouldn't worry about libpq5 11 - using the 13 version > from the "main" repository component is the recommended way. For my own understanding, what are the ramifications of using the non-"main" repository component / what are the differences? I was also under the impression that since the version number tracks the postgres release it is compatible with, that I should be choosing the version that matches the version of postgres I'm running, i.e. since I'm running Postgres 11, I should be using libpq5-11.xx. I'm primarily installing libpq for python; however, taking a closer look at psycopg2 docs (https://www.psycopg.org/docs/install.html#runtime-requirements), I see that they are in agreement with what you're saying: > Note: Whatever version of libpq psycopg2 is compiled with, it will > be possible to connect to PostgreSQL servers of any supported > version: just install the most recent libpq version or the most > practical, without trying to match it to the version of the > PostgreSQL server you will have to connect to. Out of curiosity, if we were running libpq5-11 with Postgres 13, would we see any issues or does postgres maintain backwards compatibility with these libs as well? Thanks again! Best, Saif --00000000000070012e05bb53d013 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Christoph,

> that= is indeed stale, thanks for spotting that. The problem is present
> = in the other distributions as well. I have now manually updated
> bio= nic-pgdg, but I will leave the other untouched until I can figure
=

Thanks!, I've confirmed that my repro no longer wor= ks and version 11 is installed.

> That sai= d, you shouldn't worry about libpq5 11 - using the 13 version
>= from the "main" repository component is the recommended way.=C2= =A0

For my own understanding, what are the ramific= ations of using=C2=A0the non-"main" repository component / what a= re the differences?

I was also under the impressio= n that since the version number tracks the postgres release it is compatibl= e with, that I should be choosing the version that matches the version of p= ostgres I'm running, i.e. since I'm running Postgres 11, I should b= e using libpq5-11.xx. I'm primarily installing libpq for python; howeve= r, taking a closer look at psycopg2 docs (https://www.psycopg.org/docs/inst= all.html#runtime-requirements), I see that they are in agreement with= =C2=A0what you're saying:

> Note: Whatever = version of libpq psycopg2 is compiled with, it will
> be possible to = connect to PostgreSQL servers of any supported
> version: just instal= l the most recent libpq version or the most
> practical, without tryi= ng to match it to the version of the
> PostgreSQL server you will hav= e to connect to.

Out of curiosity, if we were running lib= pq5-11 with Postgres 13, would we see any issues or does postgres maintain = backwards compatibility with these libs as well?

=
Thanks again!

Best,
Saif
--00000000000070012e05bb53d013--