Fix pgpool_setup to not confuse log output
authorTatsuo Ishii <ishii@postgresql.org>
Sat, 26 Mar 2016 22:49:53 +0000 (07:49 +0900)
committerTatsuo Ishii <ishii@postgresql.org>
Sat, 26 Mar 2016 23:04:54 +0000 (08:04 +0900)
commit8b237a77702c972647cc723393c5c7c91fcffd26
treea891eeb2e0dd47d5ea212a6f77caf616bacf120d
parent2630b771a33989d7733f670584a1252f26dc2cf5
Fix pgpool_setup to not confuse log output

Before it simply redirects the stdout and stderr of pgpool process to
a log file.  This could cause log contents being garbled or even
missed because of race condition caused by multiple process being
writing concurrently. I and Usama found this while investigating the
regression failure of 004.watchdog.

To fix this, pgpool_setup now generates startall script so that pgpool
now sends stdout/stderr to cat command and cat writes to the log file
(It seems the race condition does not occur when writing to a pipe).
src/test/pgpool_setup