pgsql: Improve stability of partition_prune regression test.
Improve stability of partition_prune regression test. This test already knew that, to get stable test output, it had to hide "loops" counts in EXPLAIN ANALYZE results. But that's not nearly enough: if we get a smaller number of workers than we planned for, then the "Workers Launched" number will change, and so will all the rows and loops counts up to the Gather node. This has resulted in repeated failures in the buildfarm, so adjust the test to filter out all these counts. (Really, we wouldn't bother with EXPLAIN ANALYZE at all here, except that currently the only way to verify that executor-time pruning has happened is to look for '(never executed)' annotations. Those are stable and needn't be filtered out.) Back-patch to v11 where the test was introduced. Discussion: https://postgr.es/m/11952.1569536...@sss.pgh.pa.us Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/0baa55655e0549cf19fcfdb007c3250f7d4761a9 Modified Files -- src/test/regress/expected/partition_prune.out | 196 +- src/test/regress/sql/partition_prune.sql | 16 ++- 2 files changed, 110 insertions(+), 102 deletions(-)
pgsql: Improve stability of partition_prune regression test.
Improve stability of partition_prune regression test. This test already knew that, to get stable test output, it had to hide "loops" counts in EXPLAIN ANALYZE results. But that's not nearly enough: if we get a smaller number of workers than we planned for, then the "Workers Launched" number will change, and so will all the rows and loops counts up to the Gather node. This has resulted in repeated failures in the buildfarm, so adjust the test to filter out all these counts. (Really, we wouldn't bother with EXPLAIN ANALYZE at all here, except that currently the only way to verify that executor-time pruning has happened is to look for '(never executed)' annotations. Those are stable and needn't be filtered out.) Back-patch to v11 where the test was introduced. Discussion: https://postgr.es/m/11952.1569536...@sss.pgh.pa.us Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/9de7ea6aca5a394dbddac4b13b475b313e352b3f Modified Files -- src/test/regress/expected/partition_prune.out | 196 +- src/test/regress/sql/partition_prune.sql | 16 ++- 2 files changed, 110 insertions(+), 102 deletions(-)
pgsql: Improve stability of partition_prune regression test.
Improve stability of partition_prune regression test. This test already knew that, to get stable test output, it had to hide "loops" counts in EXPLAIN ANALYZE results. But that's not nearly enough: if we get a smaller number of workers than we planned for, then the "Workers Launched" number will change, and so will all the rows and loops counts up to the Gather node. This has resulted in repeated failures in the buildfarm, so adjust the test to filter out all these counts. (Really, we wouldn't bother with EXPLAIN ANALYZE at all here, except that currently the only way to verify that executor-time pruning has happened is to look for '(never executed)' annotations. Those are stable and needn't be filtered out.) Back-patch to v11 where the test was introduced. Discussion: https://postgr.es/m/11952.1569536...@sss.pgh.pa.us Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4ea03f3f4eba3c76abae2e69bf48c921799a68a3 Modified Files -- src/test/regress/expected/partition_prune.out | 196 +- src/test/regress/sql/partition_prune.sql | 16 ++- 2 files changed, 110 insertions(+), 102 deletions(-)
pgsql: Fix compilation with older OpenSSL versions
Fix compilation with older OpenSSL versions Some older OpenSSL versions (0.9.8 branch) define TLS*_VERSION macros but not the corresponding SSL_OP_NO_* macro, which causes the code for handling ssl_min_protocol_version/ssl_max_protocol_version to fail to compile. To fix, add more #ifdefs and error handling. Reported-by: Victor Wagner Reviewed-by: Michael Paquier Discussion: https://www.postgresql.org/message-id/flat/20190924101859.09383b4f%40fafnir.local.vm Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4e6f101e921c9a7ff4e7fff847966b9cdd390753 Modified Files -- src/backend/libpq/be-secure-openssl.c | 48 +-- 1 file changed, 46 insertions(+), 2 deletions(-)
pgsql: Fix compilation with older OpenSSL versions
Fix compilation with older OpenSSL versions Some older OpenSSL versions (0.9.8 branch) define TLS*_VERSION macros but not the corresponding SSL_OP_NO_* macro, which causes the code for handling ssl_min_protocol_version/ssl_max_protocol_version to fail to compile. To fix, add more #ifdefs and error handling. Reported-by: Victor Wagner Reviewed-by: Michael Paquier Discussion: https://www.postgresql.org/message-id/flat/20190924101859.09383b4f%40fafnir.local.vm Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a430c7b4afe8278223541d3efee2281ee9135c1d Modified Files -- src/backend/libpq/be-secure-openssl.c | 48 +-- 1 file changed, 46 insertions(+), 2 deletions(-)
