pgsql: Fix typo.

2020-01-13 Thread Amit Kapila
Fix typo. Reported-by: Antonin Houska Author: Antonin Houska Backpatch-through: 11, where it was introduced Discussion: https://postgr.es/m/2246.1578900133@antos Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/dea88c9be27813894081d14a8160c7d2196f4415

pgsql: Fix typo.

2020-01-13 Thread Amit Kapila
Fix typo. Reported-by: Antonin Houska Author: Antonin Houska Backpatch-through: 11, where it was introduced Discussion: https://postgr.es/m/2246.1578900133@antos Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/52bc730381420a8fd9a92e633e217c8ca8c3a54b

pgsql: Fix comment in heapam.c

2020-01-13 Thread Michael Paquier
Fix comment in heapam.c Improvement per suggestion from Tom Lane. Author: Daniel Gustafsson Discussion: https://postgr.es/m/fed18699-4270-4778-8da8-10f119a5e...@yesql.se Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/7689d907bbb177fa2a8f5aca3f968761dd16bf28

pgsql: Fix base backup with database OIDs larger than INT32_MAX

2020-01-13 Thread Peter Eisentraut
Fix base backup with database OIDs larger than INT32_MAX The use of pg_atoi() for parsing a string into an Oid fails for values larger than INT32_MAX, since OIDs are unsigned. Instead, use atooid(). While this has less error checking, the contents of the data directory are expected to be

pgsql: Fix base backup with database OIDs larger than INT32_MAX

2020-01-13 Thread Peter Eisentraut
Fix base backup with database OIDs larger than INT32_MAX The use of pg_atoi() for parsing a string into an Oid fails for values larger than INT32_MAX, since OIDs are unsigned. Instead, use atooid(). While this has less error checking, the contents of the data directory are expected to be

pgsql: Reduce size of backend scanner's tables.

2020-01-13 Thread Tom Lane
Reduce size of backend scanner's tables. Previously, the core scanner's yy_transition[] array had 37045 elements. Since that number is larger than INT16_MAX, Flex generated the array to contain 32-bit integers. By reimplementing some of the bulkier scanner rules, this patch reduces the array to

pgsql: Revert test added by commit d207038053.

2020-01-13 Thread Amit Kapila
Revert test added by commit d207038053. This test was trying to test the mechanism to release kernel FDs as needed to get us under the max_safe_fds limit in case of spill files. To do that, it needs to set max_files_per_process to a very low value which doesn't even permit starting of the server

pgsql: Revert test added by commit d207038053.

2020-01-13 Thread Amit Kapila
Revert test added by commit d207038053. This test was trying to test the mechanism to release kernel FDs as needed to get us under the max_safe_fds limit in case of spill files. To do that, it needs to set max_files_per_process to a very low value which doesn't even permit starting of the server

pgsql: Revert test added by commit d207038053.

2020-01-13 Thread Amit Kapila
Revert test added by commit d207038053. This test was trying to test the mechanism to release kernel FDs as needed to get us under the max_safe_fds limit in case of spill files. To do that, it needs to set max_files_per_process to a very low value which doesn't even permit starting of the server

pgsql: Revert test added by commit d207038053.

2020-01-13 Thread Amit Kapila
Revert test added by commit d207038053. This test was trying to test the mechanism to release kernel FDs as needed to get us under the max_safe_fds limit in case of spill files. To do that, it needs to set max_files_per_process to a very low value which doesn't even permit starting of the server