Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XKG6K-0004c6-1v for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Aug 2014 00:19:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XKG6J-0007au-EC for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Aug 2014 00:19:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XKG6I-0007am-6R for pgsql-hackers@postgresql.org; Thu, 21 Aug 2014 00:19:34 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XKG6E-0000Ue-2R for pgsql-hackers@postgresql.org; Thu, 21 Aug 2014 00:19:32 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1XKG69-00051R-Qs; Wed, 20 Aug 2014 20:19:25 -0400 Date: Wed, 20 Aug 2014 20:19:25 -0400 From: Bruce Momjian To: Stephen Frost Cc: Robert Haas , Magnus Hagander , Tom Lane , Heikki Linnakangas , PostgreSQL-development Subject: Re: PQgetssl() and alternative SSL implementations Message-ID: <20140821001925.GH17822@momjian.us> References: <53F1E989.8020609@vmware.com> <10419.1408475397@sss.pgh.pa.us> <20140819194717.GM16422@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140819194717.GM16422@tamriel.snowman.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On Tue, Aug 19, 2014 at 03:47:17PM -0400, Stephen Frost wrote: > * Robert Haas (robertmhaas@gmail.com) wrote: > > BTW, if we're beating on libpq, I wonder if we shouldn't consider > > bumping the soversion at some point. I mean, I know that we > > technically don't need to do that if we're only *adding* functions and > > not changing any of the existing stuff in backward-incompatible ways, > > but we might *want* to make some backward-incompatible changes at some > > point, and I think there's a decent argument that any patch in this > > are is already doing that at least to PQgetSSL(). Maybe this would be > > a good time to think if there's anything else we want to do that > > would, either by itself or in combination, justify a bump. > > I'm not a big fan of doing it for this specific item, though it's > technically an API breakage (which means we should actually have > libpq2-dev packages, make everything that build-deps on libpq-dev > update to build-dep on libpq2-dev, have libpq6, etc..). If there are > other backwards-incompatible things we wish to do, then I agree that > it'd be good to do them all at the same time (perhaps in conjunction > with 10.0...). This is the part where I wish we had been keeping an > updated list of things we want to change (like on the wiki..). We have, called "Wire Protocol Changes": https://wiki.postgresql.org/wiki/Todo Unfortunately, the subsection link doesn't work on Firefox. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers