Skip to main content

Frequently asked questions

Does pocketPG modify my database?​

No. All monitoring connections use autocommit = True and read from system catalog views only. pocketPG never creates tables, indexes, extensions, or functions on your database. The one exception is owner-initiated maintenance (VACUUM, ANALYZE, REINDEX) which requires explicit confirmation.

What PostgreSQL versions are supported?​

PostgreSQL 12 and above. Some features require newer PostgreSQL versions or optional extensions:

  • Core monitoring works on supported PostgreSQL versions.
  • Query and tuning detail improves when newer statistics views are available.
  • Some PostgreSQL 17 autovacuum metadata is used only when the server exposes it.

Do I need to install an agent?​

No. pocketPG connects directly to your PostgreSQL instance and runs read-only queries on demand. There is no background agent, no binary to install, and no schema to create.

What is pg_stat_statements and do I need it?​

pg_stat_statements is a PostgreSQL extension that tracks query execution statistics (calls, total time, rows, temp files, etc.). It is highly recommended — without it, the Queries tab, tail latency insights, extension recommendations, and several tuning signals (work_mem spill detection, prepared statements) are unavailable.

To enable it:

CREATE EXTENSION IF NOT EXISTS pg_stat_statements;

On most managed providers (RDS, Aiven, Azure), it is pre-installed or available via a configuration toggle.

How does shared instance billing work?​

Owner-pays model. The instance owner holds the subscription. Invited members get access at no extra cost. If the owner cancels, members lose access.

Can I use pocketPG with PgBouncer?​

Connect pocketPG directly to PostgreSQL, not through PgBouncer. PgBouncer's transaction-mode pooling can interfere with SET commands and pg_stat_statements queries. pocketPG manages its own lightweight connection pool.

What data does pocketPG store?​

  • Connection credentials — stored server-side in the app database for saved instances. Members never see raw credentials.
  • Performance samples — recent samples may be stored locally and, for saved instances, server-side to support charts and history.
  • No query text — pocketPG reads query statistics from pg_stat_statements but does not store query text on its servers.

Is there a self-hosted option?​

Not currently. pocketPG is a SaaS product deployed on Railway.

How do I cancel my subscription?​

Through the LemonSqueezy billing portal, accessible from the Account tab.