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 1oktoZ-0005ho-Ot for pgsql-bugs@arkaria.postgresql.org; Tue, 18 Oct 2022 21:07:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oktoY-0007x1-Kq for pgsql-bugs@arkaria.postgresql.org; Tue, 18 Oct 2022 21:07:54 +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 1oktoY-0007ws-DF for pgsql-bugs@lists.postgresql.org; Tue, 18 Oct 2022 21:07:54 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oktoW-0006Ga-0j for pgsql-bugs@lists.postgresql.org; Tue, 18 Oct 2022 21:07:54 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 29IL7fxg2733627; Tue, 18 Oct 2022 17:07:41 -0400 From: Tom Lane To: =?UTF-8?Q?Mike_Fr=C3=B6hner?= cc: Julien Rouhaud , pgsql-bugs@lists.postgresql.org Subject: Re: =?UTF-8?Q?Aw=3A_Re=3A_=C2=A0BUG_=2317647=3A_12=2E12_packa?= =?UTF-8?Q?ge_has_difference_on_ubuntu_18=2E04?= In-reply-to: References: <17647-355ab16b3ab3c775@postgresql.org> <20221018132519.tt3feryowdyhdvbn@jrouhaud> Comments: In-reply-to =?UTF-8?Q?Mike_Fr=C3=B6hner?= message dated "Tue, 18 Oct 2022 20:13:34 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2733625.1666127261.1@sss.pgh.pa.us> Date: Tue, 18 Oct 2022 17:07:41 -0400 Message-ID: <2733626.1666127261@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =?UTF-8?Q?Mike_Fr=C3=B6hner?= writes: > But to ensure we understand correctly - I am not talking about pg14 or > pg15. We have noticed the changed behavior ONLY while using > postgresql-12 package on Ubuntu 18.04 with libpq5 upgraded from > 14.5-1.pgdg18.04+1 to 15.0-1.pgdg18.04+1 and postgresql-client-common + > postgresql-common upgraded from 243.pgdg18.04+1 to 244.pgdg18.04+1. It's libpq that determines this behavior, not the server, so I find nothing whatever surprising in your statement. > For now I am fine with adjusted command in our testing suite. But it is > still strange the same command works on all versions of Ubuntu LTS but > not on Ubuntu 18.04. Probably they've not updated libpq so quickly in the LTS distros. regards, tom lane