pgsql: Disable one more set of tests from c8841199509.

2019-10-05 Thread Andres Freund
Disable one more set of tests from c8841199509. Discussion: https://postgr.es/m/[email protected] Backpatch: 9.6-, just like c8841199509 and 6e61d75f525 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/77b2d95b1485091c70fc48ed6

pgsql: Disable one more set of tests from c8841199509.

2019-10-05 Thread Andres Freund
Disable one more set of tests from c8841199509. Discussion: https://postgr.es/m/[email protected] Backpatch: 9.6-, just like c8841199509 and 6e61d75f525 Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/2212e01316ff421300d0a0d20

pgsql: Disable one more set of tests from c8841199509.

2019-10-05 Thread Andres Freund
Disable one more set of tests from c8841199509. Discussion: https://postgr.es/m/[email protected] Backpatch: 9.6-, just like c8841199509 and 6e61d75f525 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3a68105154c3a35e4b107b41e2f54ec8

pgsql: Disable one more set of tests from c8841199509.

2019-10-05 Thread Andres Freund
Disable one more set of tests from c8841199509. Discussion: https://postgr.es/m/[email protected] Backpatch: 9.6-, just like c8841199509 and 6e61d75f525 Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/9051f62ed7eff9eb01e4fa7a3

pgsql: Disable one more set of tests from c8841199509.

2019-10-05 Thread Andres Freund
Disable one more set of tests from c8841199509. Discussion: https://postgr.es/m/[email protected] Backpatch: 9.6-, just like c8841199509 and 6e61d75f525 Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/04a4c03efe3e4b0cbccb7a7e2

pgsql: Avoid use of wildcard in pg_waldump's .gitignore.

2019-10-05 Thread Tom Lane
Avoid use of wildcard in pg_waldump's .gitignore. This would be all right, maybe, if it didn't also match a file that definitely should not be ignored. We don't add rmgrs so often that manual maintenance of this file list is impractical, so just write out the list. (I find the equivalent wildcar

pgsql: Avoid use of wildcard in pg_waldump's .gitignore.

2019-10-05 Thread Tom Lane
Avoid use of wildcard in pg_waldump's .gitignore. This would be all right, maybe, if it didn't also match a file that definitely should not be ignored. We don't add rmgrs so often that manual maintenance of this file list is impractical, so just write out the list. (I find the equivalent wildcar

pgsql: Avoid use of wildcard in pg_waldump's .gitignore.

2019-10-05 Thread Tom Lane
Avoid use of wildcard in pg_waldump's .gitignore. This would be all right, maybe, if it didn't also match a file that definitely should not be ignored. We don't add rmgrs so often that manual maintenance of this file list is impractical, so just write out the list. (I find the equivalent wildcar

pgsql: Avoid use of wildcard in pg_waldump's .gitignore.

2019-10-05 Thread Tom Lane
Avoid use of wildcard in pg_waldump's .gitignore. This would be all right, maybe, if it didn't also match a file that definitely should not be ignored. We don't add rmgrs so often that manual maintenance of this file list is impractical, so just write out the list. (I find the equivalent wildcar

pgsql: Report test_atomic_ops() failures consistently, via macros.

2019-10-05 Thread Noah Misch
Report test_atomic_ops() failures consistently, via macros. This prints the unexpected value in more failure cases, and it removes forty-eight hand-maintained error messages. Back-patch to 9.5, which introduced these tests. Reviewed (in an earlier version) by Andres Freund. Discussion: https://

pgsql: Report test_atomic_ops() failures consistently, via macros.

2019-10-05 Thread Noah Misch
Report test_atomic_ops() failures consistently, via macros. This prints the unexpected value in more failure cases, and it removes forty-eight hand-maintained error messages. Back-patch to 9.5, which introduced these tests. Reviewed (in an earlier version) by Andres Freund. Discussion: https://

pgsql: Report test_atomic_ops() failures consistently, via macros.

2019-10-05 Thread Noah Misch
Report test_atomic_ops() failures consistently, via macros. This prints the unexpected value in more failure cases, and it removes forty-eight hand-maintained error messages. Back-patch to 9.5, which introduced these tests. Reviewed (in an earlier version) by Andres Freund. Discussion: https://

pgsql: Report test_atomic_ops() failures consistently, via macros.

2019-10-05 Thread Noah Misch
Report test_atomic_ops() failures consistently, via macros. This prints the unexpected value in more failure cases, and it removes forty-eight hand-maintained error messages. Back-patch to 9.5, which introduced these tests. Reviewed (in an earlier version) by Andres Freund. Discussion: https://

pgsql: Report test_atomic_ops() failures consistently, via macros.

2019-10-05 Thread Noah Misch
Report test_atomic_ops() failures consistently, via macros. This prints the unexpected value in more failure cases, and it removes forty-eight hand-maintained error messages. Back-patch to 9.5, which introduced these tests. Reviewed (in an earlier version) by Andres Freund. Discussion: https://

pgsql: Report test_atomic_ops() failures consistently, via macros.

2019-10-05 Thread Noah Misch
Report test_atomic_ops() failures consistently, via macros. This prints the unexpected value in more failure cases, and it removes forty-eight hand-maintained error messages. Back-patch to 9.5, which introduced these tests. Reviewed (in an earlier version) by Andres Freund. Discussion: https://

pgsql: Change MemoryContextMemAllocated to return Size

2019-10-05 Thread Tomas Vondra
Change MemoryContextMemAllocated to return Size Commit f2369bc610 switched most of the memory accounting from int64 to Size, but it forgot to change the MemoryContextMemAllocated return type. So this fixes that omission. Discussion: https://www.postgresql.org/message-id/11238.1570200198%40sss.pg