What dependencies does pganalyze have?
pganalyze requires a PostgreSQL 9.2 or newer database with the pg_stat_statements extension installed. The collector which regularly posts statistics to our service requires Python 2.6 or newer.
What are the performance implications of pganalyze?
The performance overhead of the pg_stat_statements extension is small - it requires a bit of additional shared memory and will consume about ~1% of CPU time. The impact of the collector script which parses the data and submits it to pganalyze is negligible.
What data gets sent to pganalyze?
The collector agent posts the following information on each invocation:
OS performance data
The database schema
- Table definition
Information about the queries that have been run
- Normalized query with all values replaced by placeholders
- The plan of the query
- An example query including values
- Performance values for the query
Do you offer local installations?
Yes, we are working on offering an option for local installation, please contact us for specific details.
Do you need admin/superuser access to my database?
Our collector script needs superuser access for fetching the query information from your database, which is then submitted via API to our servers. We don't store any of your user/password information on our server.
This collector script is open-source: pganalyze-collector
Are versions older than PostgreSQL 9.2 supported?
pganalyze works only with PostgreSQL 9.2 or newer. Previous versions ship with pg_stat_statements but due to design limitations in the older versions of the extension the queries it collects aren't normalized and cannot be used for statistical analysis.
When am I going to get billed?
Plans are billed on a monthly basis - annual payment is available upon request.