Closed galeone closed 8 years ago
Hi !
The bug you are experiencing is not present in the latest release of pg_qualstats (0.0.6). It has been introduced on the master, not yet released, branch, but has been corrected in the "devel" branch which should be merged (and released!) soon.
So, either use the devel branch (not recommended) or install a stable, released version (recommended).
Thank you !
Hi, thank you for the quick reply.
I'm going to follow the [official guide](https://powa.readthedocs.org/en/latest/stats_extensions/pg_qualstats.html] to setup pg_qualstats) instead of follow only the quick-start guide (as I did, thus I encountered this problem).
You can close the issue if you want.
Thank you
Hi, before powa installation the query
works without any problem.
Here's a
explain verbose
output of the query (maybe it can be helpful):After powa installation, the same query output is:
In addiction, application connected to postgres have logs full of this error: (here's an example of a php application, conneted via PDO to postgresql).
Disabling powa (commenting out the 4 lines below) everything comes back to the original state, and everything works well.
I found powa really helpful (tuning the DB its so much easier now) thus I hope you can fix this issue ASAP, so I can re-enable it on my server and continuing the tuning.
Thank you.
P.S: if you want the schema structure (the schema on which I run the query above) you can find it here: nerdz-test-db
My PostgreSQL server version is: 9.4.4
Thank you