When using a custom CachePath calling Stop() shuts down
the postgres process but does not remove the cache directory.
Over
repeated test runs, these directories accumulate in the CachePath and currently I clean it manually.
Start() already cleans up runtimePath on each invocation, but there
is no equivalent cleanup for CachePath on Stop().
Is this intended ?
When using a custom
CachePathcalling Stop() shuts downthe postgres process but does not remove the cache directory.
Over
repeated test runs, these directories accumulate in the CachePath and currently I clean it manually.
Start() already cleans up runtimePath on each invocation, but there
is no equivalent cleanup for CachePath on Stop().
Is this intended ?