Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goVja-0004Bi-3Y for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Jan 2019 15:55:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1goVjY-0002ls-QH for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Jan 2019 15:55:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goVjY-0002lV-GT for pgsql-hackers@lists.postgresql.org; Tue, 29 Jan 2019 15:55:32 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1goVjW-0007fx-4N for pgsql-hackers@postgresql.org; Tue, 29 Jan 2019 15:55:32 +0000 Received: from msg.df7cb.de (unknown [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 43prgP3Y4Zz3F1K; Tue, 29 Jan 2019 16:55:29 +0100 (CET) Date: Tue, 29 Jan 2019 16:55:29 +0100 From: Christoph Berg To: Tom Lane Cc: PostgreSQL Hackers Subject: Re: pgsql: Build src/port files as a library with -fPIC, and use that in li Message-ID: <20190129155528.GK9860@msg.df7cb.de> Mail-Followup-To: Christoph Berg , Tom Lane , PostgreSQL Hackers References: <20180928115830.GC26142@msg.df7cb.de> <19404.1538140436@sss.pgh.pa.us> <20180928132013.GE26142@msg.df7cb.de> <20671.1538142538@sss.pgh.pa.us> <20190129140437.GF9860@msg.df7cb.de> <27653.1548774621@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27653.1548774621@sss.pgh.pa.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Re: Tom Lane 2019-01-29 <27653.1548774621@sss.pgh.pa.us> > > It took a while to notice, but this change does break 8.2's initdb if > > libpq5 from PG12 is installed: > > $ /usr/lib/postgresql/8.2/bin/initdb > > /usr/lib/postgresql/8.2/bin/initdb: symbol lookup error: /usr/lib/postgresql/8.2/bin/initdb: undefined symbol: pqsignal > > Well, 8.2 is *very* long out of support, and there are plenty of > nasty bugs you're at risk of if you keep using it. So I don't > find this to be a good argument for contorting what we do in v12. I try to keep the old versions alive on apt.pg.o for Debian unstable (only) so I have something to grab when customers ask questions about the old versions. We are probably lucky that 8.2 broke only now, and leaving it broken is a fair thing. I was just mentioning for completeness, I didn't mean to insist on fixing it. > If you really want to keep using 8.2 (and even make new installations > with it!?), you could back-patch the 8.3 patch that made sure that > initdb didn't absorb pqsignal, pg_encoding_to_char, etc from libpq. > It looks like what you'd need is a portion of the Makefile changes > from 8468146b03c87f86162cee62e0de25f6e2d24b56. I might give that a shot, but if it's too hard, dropping 8.2 "support" is not a problem. Thanks for digging up the commit hash. Christoph