From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | some PostgreSQL 12 release notes comments |
Date: | 2019-09-17 17:09:09 |
Message-ID: | d4dff575-90ab-9c8c-cc6f-8c657e2de665@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> * Client- and server-side encryption for authentication using GSSAPI
This is on the wire encryption, so I don't know why it says client-side
and server-side. Proposal:
* Encrypted TCP/IP connections using GSSAPI encryption
in the major features section, and later
* Add GSSAPI encryption support (Robbie Harwood, Stephen Frost)
This allows TCP/IP connections to be encrypted when using GSSAPI
authentication without having to set up a separate encryption facility
like SSL.
> * Discovery of LDAP servers if PostgreSQL is built with OpenLDAP
I would remove the "if" part from the major features list, since it's a
qualification of minor importance. Instead I'd write something like
* Discovery of LDAP servers using DNS SRV
which is a clearer concept that people can easily recognize.
> * Allow data type name to use non-C collations
I'm not sure why that is listed in the "Migration" section.
It's also a bit confusing as a release note item relative to PostgreSQL
11. I believe the changes were that "name" was made collation aware and
that the collation was set to "C" in the system catalogs (which is a
separate item later). This group of items could use a reshuffling.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-09-17 17:37:42 | Re: Allow an alias to be attached directly to a JOIN ... USING |
Previous Message | Tom Lane | 2019-09-17 17:00:09 | Re: Leakproofness of texteq()/textne() |