pgsql: Remove obsolete ifdefs

2020-10-21 Thread Peter Eisentraut
Remove obsolete ifdefs Commit 8dace66e0735ca39b779922d02c24ea2686e6521 added #ifdefs for a number of errno symbols because they were not present on Windows. Later, commit 125ad539a275db5ab8f4647828b80a16d02eabd2 added replacement #defines for some of those symbols. So some of the changes from the

pgsql: Remove the option to build thread_test.c outside configure.

2020-10-21 Thread Tom Lane
Remove the option to build thread_test.c outside configure. Theoretically one could go into src/test/thread and build/run this program there. In practice, that hasn't worked since 96bf88d52, and probably much longer on some platforms (likely including just the sort of hoary leftovers where this t

pgsql: Use fast checkpoint in PostgresNode::backup()

2020-10-21 Thread Alvaro Herrera
Use fast checkpoint in PostgresNode::backup() Should cause tests to be a bit faster Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/831611b11c34ed0066633864f42ff67a10286aee Modified Files -- src/test/perl/PostgresNode.pm | 6 -- 1 file changed, 4 ins

pgsql: Use fast checkpoint in PostgresNode::backup()

2020-10-21 Thread Alvaro Herrera
Use fast checkpoint in PostgresNode::backup() Should cause tests to be a bit faster Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/ddc728d437a08c68638101ef01d742d6f4476675 Modified Files -- src/test/perl/PostgresNode.pm | 6 -- 1 file changed

pgsql: Use fast checkpoint in PostgresNode::backup()

2020-10-21 Thread Alvaro Herrera
Use fast checkpoint in PostgresNode::backup() Should cause tests to be a bit faster Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/35b4b7d0851444904f450805880f30b6cc49c514 Modified Files -- src/test/perl/PostgresNode.pm | 6 -- 1 file changed

pgsql: Use fast checkpoint in PostgresNode::backup()

2020-10-21 Thread Alvaro Herrera
Use fast checkpoint in PostgresNode::backup() Should cause tests to be a bit faster Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a818000f6a88cfe39e3751f5bedf40dd5294433b Modified Files -- src/test/perl/PostgresNode.pm | 6 -- 1 file changed

pgsql: Use fast checkpoint in PostgresNode::backup()

2020-10-21 Thread Alvaro Herrera
Use fast checkpoint in PostgresNode::backup() Should cause tests to be a bit faster Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/c7658a470a2986b2c84553f3193972b0b868b74b Modified Files -- src/test/perl/PostgresNode.pm | 6 -- 1 file changed

pgsql: Fix connection string handling in psql's \connect command.

2020-10-21 Thread Tom Lane
Fix connection string handling in psql's \connect command. psql's \connect claims to be able to re-use previous connection parameters, but in fact it only re-uses the database name, user name, host name (and possibly hostaddr, depending on version), and port. This is problematic for assorted use c

pgsql: Fix connection string handling in psql's \connect command.

2020-10-21 Thread Tom Lane
Fix connection string handling in psql's \connect command. psql's \connect claims to be able to re-use previous connection parameters, but in fact it only re-uses the database name, user name, host name (and possibly hostaddr, depending on version), and port. This is problematic for assorted use c

pgsql: Fix connection string handling in psql's \connect command.

2020-10-21 Thread Tom Lane
Fix connection string handling in psql's \connect command. psql's \connect claims to be able to re-use previous connection parameters, but in fact it only re-uses the database name, user name, host name (and possibly hostaddr, depending on version), and port. This is problematic for assorted use c

pgsql: Fix connection string handling in psql's \connect command.

2020-10-21 Thread Tom Lane
Fix connection string handling in psql's \connect command. psql's \connect claims to be able to re-use previous connection parameters, but in fact it only re-uses the database name, user name, host name (and possibly hostaddr, depending on version), and port. This is problematic for assorted use c

pgsql: Fix connection string handling in psql's \connect command.

2020-10-21 Thread Tom Lane
Fix connection string handling in psql's \connect command. psql's \connect claims to be able to re-use previous connection parameters, but in fact it only re-uses the database name, user name, host name (and possibly hostaddr, depending on version), and port. This is problematic for assorted use c

pgsql: Fix connection string handling in psql's \connect command.

2020-10-21 Thread Tom Lane
Fix connection string handling in psql's \connect command. psql's \connect claims to be able to re-use previous connection parameters, but in fact it only re-uses the database name, user name, host name (and possibly hostaddr, depending on version), and port. This is problematic for assorted use c

pgsql: Fix connection string handling in psql's \connect command.

2020-10-21 Thread Tom Lane
Fix connection string handling in psql's \connect command. psql's \connect claims to be able to re-use previous connection parameters, but in fact it only re-uses the database name, user name, host name (and possibly hostaddr, depending on version), and port. This is problematic for assorted use c

pgsql: Optimize a few list_delete_ptr calls

2020-10-21 Thread David Rowley
Optimize a few list_delete_ptr calls There is a handful of places where we called list_delete_ptr() to remove some element from a List. In many of these places we know, or with very little additional effort know the index of the ListCell that we need to remove. Here we change all of those places