projects / pgpool2.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b96cea6) | patch
Test: fix occasional 069.memory_leak_extended test failure.
authorTatsuo Ishii <ishii@sraoss.co.jp>
Mon, 22 May 2023 07:27:40 +0000 (16:27 +0900)
committerTatsuo Ishii <ishii@sraoss.co.jp>
Mon, 22 May 2023 07:33:13 +0000 (16:33 +0900)
commitd3f1b4b6df83194c116936a8f1113b65c2287d24
treee77e2bfc38da0de3e2b3bf3bcd49c3e06382cf23tree
parentb96cea6eecc610a826d968414ecad884611648a6commit | diff
Test: fix occasional 069.memory_leak_extended test failure.

It turned out that reason of the occasional test failure is, pgpool
child process is gone before running ps command after pgbench
finishes. The cause is a kind mismatch FATAL error, "DISCARD ALL
cannot be executed within a pipeline". To fix this, run pgbench in
background and get the process size before pgbench finishes.

Discussion: https://www.pgpool.net/pipermail/pgpool-hackers/2023-May/004338.html
src/test/regression/tests/069.memory_leak_extended/test.sh diff | blob | blame | history
Clustering tool for PostgreSQL