pgsql: Fix ancient violation of zlib's API spec.

2020-07-23 Thread Tom Lane
Fix ancient violation of zlib's API spec. contrib/pgcrypto mishandled the case where deflate() does not consume all of the offered input on the first try. It reset the next_in pointer to the start of the input instead of leaving it alone, causing the wrong data to be fed to the next deflate() cal

pgsql: Fix ancient violation of zlib's API spec.

2020-07-23 Thread Tom Lane
Fix ancient violation of zlib's API spec. contrib/pgcrypto mishandled the case where deflate() does not consume all of the offered input on the first try. It reset the next_in pointer to the start of the input instead of leaving it alone, causing the wrong data to be fed to the next deflate() cal

pgsql: Fix ancient violation of zlib's API spec.

2020-07-23 Thread Tom Lane
Fix ancient violation of zlib's API spec. contrib/pgcrypto mishandled the case where deflate() does not consume all of the offered input on the first try. It reset the next_in pointer to the start of the input instead of leaving it alone, causing the wrong data to be fed to the next deflate() cal

pgsql: Fix ancient violation of zlib's API spec.

2020-07-23 Thread Tom Lane
Fix ancient violation of zlib's API spec. contrib/pgcrypto mishandled the case where deflate() does not consume all of the offered input on the first try. It reset the next_in pointer to the start of the input instead of leaving it alone, causing the wrong data to be fed to the next deflate() cal

pgsql: Fix ancient violation of zlib's API spec.

2020-07-23 Thread Tom Lane
Fix ancient violation of zlib's API spec. contrib/pgcrypto mishandled the case where deflate() does not consume all of the offered input on the first try. It reset the next_in pointer to the start of the input instead of leaving it alone, causing the wrong data to be fed to the next deflate() cal

pgsql: Fix ancient violation of zlib's API spec.

2020-07-23 Thread Tom Lane
Fix ancient violation of zlib's API spec. contrib/pgcrypto mishandled the case where deflate() does not consume all of the offered input on the first try. It reset the next_in pointer to the start of the input instead of leaving it alone, causing the wrong data to be fed to the next deflate() cal

pgsql: Fix ancient violation of zlib's API spec.

2020-07-23 Thread Tom Lane
Fix ancient violation of zlib's API spec. contrib/pgcrypto mishandled the case where deflate() does not consume all of the offered input on the first try. It reset the next_in pointer to the start of the input instead of leaving it alone, causing the wrong data to be fed to the next deflate() cal

pgsql: doc: Document that ssl_ciphers does not affect TLS 1.3

2020-07-23 Thread Peter Eisentraut
doc: Document that ssl_ciphers does not affect TLS 1.3 TLS 1.3 uses a different way of specifying ciphers and a different OpenSSL API. PostgreSQL currently does not support setting those ciphers. For now, just document this. In the future, support for this might be added somehow. Reviewed-by:

pgsql: doc: Document that ssl_ciphers does not affect TLS 1.3

2020-07-23 Thread Peter Eisentraut
doc: Document that ssl_ciphers does not affect TLS 1.3 TLS 1.3 uses a different way of specifying ciphers and a different OpenSSL API. PostgreSQL currently does not support setting those ciphers. For now, just document this. In the future, support for this might be added somehow. Reviewed-by:

pgsql: doc: Document that ssl_ciphers does not affect TLS 1.3

2020-07-23 Thread Peter Eisentraut
doc: Document that ssl_ciphers does not affect TLS 1.3 TLS 1.3 uses a different way of specifying ciphers and a different OpenSSL API. PostgreSQL currently does not support setting those ciphers. For now, just document this. In the future, support for this might be added somehow. Reviewed-by:

pgsql: doc: Document that ssl_ciphers does not affect TLS 1.3

2020-07-23 Thread Peter Eisentraut
doc: Document that ssl_ciphers does not affect TLS 1.3 TLS 1.3 uses a different way of specifying ciphers and a different OpenSSL API. PostgreSQL currently does not support setting those ciphers. For now, just document this. In the future, support for this might be added somehow. Reviewed-by:

pgsql: doc: Document that ssl_ciphers does not affect TLS 1.3

2020-07-23 Thread Peter Eisentraut
doc: Document that ssl_ciphers does not affect TLS 1.3 TLS 1.3 uses a different way of specifying ciphers and a different OpenSSL API. PostgreSQL currently does not support setting those ciphers. For now, just document this. In the future, support for this might be added somehow. Reviewed-by:

pgsql: doc: Document that ssl_ciphers does not affect TLS 1.3

2020-07-23 Thread Peter Eisentraut
doc: Document that ssl_ciphers does not affect TLS 1.3 TLS 1.3 uses a different way of specifying ciphers and a different OpenSSL API. PostgreSQL currently does not support setting those ciphers. For now, just document this. In the future, support for this might be added somehow. Reviewed-by:

pgsql: doc: Document that ssl_ciphers does not affect TLS 1.3

2020-07-23 Thread Peter Eisentraut
doc: Document that ssl_ciphers does not affect TLS 1.3 TLS 1.3 uses a different way of specifying ciphers and a different OpenSSL API. PostgreSQL currently does not support setting those ciphers. For now, just document this. In the future, support for this might be added somehow. Reviewed-by:

pgsql: Fix error message.

2020-07-23 Thread Thomas Munro
Fix error message. Remove extra space. Back-patch to all releases, like commit 7897e3bb. Author: Lu, Chenyang Discussion: https://postgr.es/m/795d03c6129844d3803e7eea48f5af0d%40G08CNEXMBPEKD04.g08.fujitsu.local Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitd

pgsql: Fix error message.

2020-07-23 Thread Thomas Munro
Fix error message. Remove extra space. Back-patch to all releases, like commit 7897e3bb. Author: Lu, Chenyang Discussion: https://postgr.es/m/795d03c6129844d3803e7eea48f5af0d%40G08CNEXMBPEKD04.g08.fujitsu.local Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitd

pgsql: Fix error message.

2020-07-23 Thread Thomas Munro
Fix error message. Remove extra space. Back-patch to all releases, like commit 7897e3bb. Author: Lu, Chenyang Discussion: https://postgr.es/m/795d03c6129844d3803e7eea48f5af0d%40G08CNEXMBPEKD04.g08.fujitsu.local Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitd

pgsql: Fix error message.

2020-07-23 Thread Thomas Munro
Fix error message. Remove extra space. Back-patch to all releases, like commit 7897e3bb. Author: Lu, Chenyang Discussion: https://postgr.es/m/795d03c6129844d3803e7eea48f5af0d%40G08CNEXMBPEKD04.g08.fujitsu.local Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitd

pgsql: Fix error message.

2020-07-23 Thread Thomas Munro
Fix error message. Remove extra space. Back-patch to all releases, like commit 7897e3bb. Author: Lu, Chenyang Discussion: https://postgr.es/m/795d03c6129844d3803e7eea48f5af0d%40G08CNEXMBPEKD04.g08.fujitsu.local Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitd

pgsql: Fix error message.

2020-07-23 Thread Thomas Munro
Fix error message. Remove extra space. Back-patch to all releases, like commit 7897e3bb. Author: Lu, Chenyang Discussion: https://postgr.es/m/795d03c6129844d3803e7eea48f5af0d%40G08CNEXMBPEKD04.g08.fujitsu.local Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitd

pgsql: Fix error message.

2020-07-23 Thread Thomas Munro
Fix error message. Remove extra space. Back-patch to all releases, like commit 7897e3bb. Author: Lu, Chenyang Discussion: https://postgr.es/m/795d03c6129844d3803e7eea48f5af0d%40G08CNEXMBPEKD04.g08.fujitsu.local Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/42d