| Age | Commit message (Collapse) | Author |
|---|
|
The pgbench directory and other utilities have moved around. Compensate
by testing if the directory exists and try to install that component.
|
|
|
|
The memory calculations for pgbench will need to be platform specific.
Also the system data collection may have to be platform specific. Thus
far, just added conditions so that things will run on FreeBSD now.
|
|
Keep the json results document small by saving log information
externally. This include:
* postgres log
* pgbench output
* sar output
|
|
The env parameter to call() was clearing the PATH environment to only
have the postgres binary install path. Modify only the PATH
environment.
|
|
Prior to 9.5, pgbench was in contrib.
|
|
This allows testing of older versions of postgres. Otherwise only
versions of postgres supporting ALTER SYSTEM (9.4+) will work with this
client.
|
|
|
|
Otherwise the messages may get buffered for a quite long time, which
is annoying, particularly in multi-process system.
|
|
In case of connection failure (e.g. a backend getting terminated by
OOM killer and taking down the whole server), the workers failed
with an exception without putting a result into the queue, leading
to hangs.
This fixes that by making the workers resilient to connection issues
by catching the exceptions and terminating nicely. Also, we retry
connection several times, to continue with benchmarking even after
OOM hits us unexpectedly, etc.
|
|
When refreshing a reporitory clone, running 'git pull $dir' does
not do the trick - it assumes the CWD is the clone, and imports
data from repository at $dir. So we need to set CWD properly and
do just 'git pull'.
Also, prefix class members with 'self'.
|
|
|
