Lukas Fittl
Lukas Fittl
> > 1. Memory leak in the Postgres parser library that the pganalyze collector utilizes - this has been confirmed in a particular edge case, and a fix is available...
@dbamohsin @JordanP Whilst not directly an update on the memory leak, it might be worth deploying the new collector release 0.38.1, which has upgrade to the new query parser version....
@aherkarsatish11 Thanks for reaching out - we're currently reviewing what we can do so the collector image can run on OpenShift. For context, the collector image today already drops privileges...
See https://github.com/pganalyze/collector/pull/174
@once-ler It seems you'll need to remove the volumes and have an empty data directory, since you can't re-use the Postgres 9.6 data directory when running on 10. Whilst there...
@once-ler I'm wondering if the worker nodes correctly registered - what does `docker ps` show?
Yes, at this point Windows is unfortunately not supported for libpg_query - the error above probably is caused by a compilation error in the C library code itself.
Apart from the makefiles the other issue is that the extracted code from Postgres is currently not supporting Windows. I've created https://github.com/lfittl/libpg_query/issues/44 to track this on the libpg_query repo itself.
> PR #238 unblocks me. I'd like to get it out in a release. Thanks for your patience here - after we get the changelog updated (see my comment), and...
Done in #257 and released to Rubygems. Thanks @stanhu for the help!