6 Commits

Author SHA1 Message Date
Markos Fountoulakis
59d868bdf1 Run sanitizer tests on PG12
Change sanitizer test to run on PG12 and make it use the same
infrastructure as the other linux regression tests.

Co-authored-by: Sven Klemm <sven@timescale.com>
2021-06-22 11:42:48 +03:00
Sven Klemm
4d871cbd26 Make readme names consistant
Most places in the source tree use README.md as filename for
additional documentation. This patch changes the filenames of
files using a different capitalization.
2021-03-26 10:03:44 +01:00
Sven Klemm
ec41593978 Ignore memory leaks in openssl code
Ignore memory leaks in openssl code when running sanitizer tests
in CI.
2020-10-05 17:38:00 +02:00
Joshua Lockerman
1cc1b7c14e Fix memory leaks part 1: BGWs
This commit fixes memory leaks in the Background Worker infrastructure.
Notably, it fixes a leak in the launcher and BGW scheduler where shared
message queue handles would not be freed, and it fixes a leak where
BackgroundWorkerHandles were not freed in the scheduler.
2019-10-02 15:54:39 -04:00
Joshua Lockerman
dbe2bab392 Add array_unnest to alignment supressions it looks like trigger lookup triggers it 2019-04-01 12:14:16 -04:00
Joshua Lockerman
bf3b3b8a69 Add sanitizer based tests
This commit adds a sanitizer run script, and updates travis to
run it in our nightly builds. Valgrind has been very slow and
unstable, so much so that we only run it during pre-release
tests, and even then it doesn't necissarily provide useful
output. The sanitizer tests run about 10x faster, and seem
stable.

We currently only run ASan and UBSan, as MSan has too many
issues within postgres's own initialization functions. As MSan
cannot be added to a binary that enables ASan, it would require
separate jobs anyway.
2019-02-13 18:12:43 -05:00