pgsql: Remove support for Python older than 2.6

2020-01-08 Thread Peter Eisentraut
Remove support for Python older than 2.6 Supporting very old Python versions is a maintenance burden, especially with the several variant test files to maintain for Python <2.6. Since we have dropped support for older OpenSSL versions in 7b283d0e1d1d79bf1c962d790c94d2a53f3bb38a, RHEL 5 is now

pgsql: Modernize Python exception syntax in tests

2020-01-08 Thread Peter Eisentraut
Modernize Python exception syntax in tests Change the exception syntax used in the tests to use the more current except Exception as ex: rather than the old except Exception, ex: Since support for Python <2.6 has been removed, all supported versions now support the new style, and we

pgsql: Reimplement nullification of walsender timestamp

2020-01-08 Thread Alvaro Herrera
Reimplement nullification of walsender timestamp Make the value null only at pg_stat_activity-output time, as suggested by Tom Lane, instead of messing with the internal state. This should appease buildfarm members with force_parallel_mode=regress, which are running parallel queries on logical

pgsql: Reimplement nullification of walsender timestamp

2020-01-08 Thread Alvaro Herrera
Reimplement nullification of walsender timestamp Make the value null only at pg_stat_activity-output time, as suggested by Tom Lane, instead of messing with the internal state. This should appease buildfarm members with force_parallel_mode=regress, which are running parallel queries on logical

pgsql: Reimplement nullification of walsender timestamp

2020-01-08 Thread Alvaro Herrera
Reimplement nullification of walsender timestamp Make the value null only at pg_stat_activity-output time, as suggested by Tom Lane, instead of messing with the internal state. This should appease buildfarm members with force_parallel_mode=regress, which are running parallel queries on logical

pgsql: Reimplement nullification of walsender timestamp

2020-01-08 Thread Alvaro Herrera
Reimplement nullification of walsender timestamp Make the value null only at pg_stat_activity-output time, as suggested by Tom Lane, instead of messing with the internal state. This should appease buildfarm members with force_parallel_mode=regress, which are running parallel queries on logical

pgsql: Improve the handling of result type coercions in SQL functions.

2020-01-08 Thread Tom Lane
Improve the handling of result type coercions in SQL functions. Use the parser's standard type coercion machinery to convert the output column(s) of a SQL function's final SELECT or RETURNING to the type(s) they should have according to the function's declared result type. We'll allow any case

pgsql: Improve GSSAPI Encryption startup comment in libpq

2020-01-08 Thread Stephen Frost
Improve GSSAPI Encryption startup comment in libpq The original comment was a bit confusing, pointed out by Alvaro Herrera. Thread: https://postgr.es/m/20191224151520.GA16435%40alvherre.pgsql Branch -- master Details ---

pgsql: Fix handling of generated columns in ALTER TABLE.

2020-01-08 Thread Tom Lane
Fix handling of generated columns in ALTER TABLE. ALTER TABLE failed if a column referenced in a GENERATED expression had been added or changed in type earlier in the ALTER command. That's because the GENERATED expression needs to be evaluated against the table's updated tuples, but it was being

pgsql: Fix handling of generated columns in ALTER TABLE.

2020-01-08 Thread Tom Lane
Fix handling of generated columns in ALTER TABLE. ALTER TABLE failed if a column referenced in a GENERATED expression had been added or changed in type earlier in the ALTER command. That's because the GENERATED expression needs to be evaluated against the table's updated tuples, but it was being

pgsql: pgbench: Use common logging API

2020-01-08 Thread Peter Eisentraut
pgbench: Use common logging API Author: Fabien COELHO Reviewed-by: Michael Paquier Reviewed-by: Peter Eisentraut Discussion: https://www.postgresql.org/message-id/flat/alpine.DEB.2.21.1912241100390.3339@pseudo Branch -- master Details ---