Free PostgreSQL snapshot review
Run one read-only script against your database and send me the output. I'll email 3 findings covering what stands out, why it matters and what I'd check next.
Free, no call needed. I review up to 5 snapshots a month from companies running PostgreSQL in production. I first check that the output is usable and the request fits. If it doesn't, or the month is full, I'll tell you within 1 business day. Accepted snapshots get 3 written findings within 2 business days of acceptance.
1. Download the script
Download walstack-snapshot.sql2. Run it during a busy period
Use PostgreSQL 13 or newer on RDS, Aurora or a self-managed server. Use an account with pg_monitor, PostgreSQL's built-in monitoring role. On RDS or Aurora, an administrator can grant it with GRANT pg_monitor TO <user>;.
Open a terminal in the script's folder. Replace the host, user and database names with your own.
psql -X -h <host> -p 5432 -U <user> -d <database> \
-f walstack-snapshot.sql -o walstack-snapshot-1.txtOne run is fine. If you can, run it again about an hour later. Change the output filename to walstack-snapshot-2.txt.
Comparing two runs shows what's growing now. A single run gives totals since statistics were last reset.
The script usually takes a few seconds. Each statement has a 10-second timeout. If it waits on a lock for one second, the script continues to the next statement.
3. Check what you're sharing
What it reads
- PostgreSQL's own statistics and catalog, including settings, expensive queries, table and index activity, and index definitions.
- Foreign keys that may need a supporting index, blocked sessions, connections, cleanup activity and replication health.
- Column names and types for the 10 largest tables. Add
-v show_schema=offto the command to omit the column listing. Index and foreign key definitions can still contain column names.
What it leaves alone
- It doesn't read rows from your application tables, write data, change persistent settings or create objects.
- It doesn't run your queries or ask PostgreSQL to explain their execution plans.
- It doesn't record host names or IP addresses. It does include database, table, index and role names.
- PostgreSQL usually replaces query values with markers like
$1and$2. Some statements, such asALTER ROLE … PASSWORD, keep their literal values. The script replaces any query text that mentions a password, secret, token or API key with a placeholder. Sensitive text can still appear, so add-v show_query_text=offto omit query text entirely. Findings are less specific without it.
Read every file before sending. Delete anything you don't want to share, including sensitive names or details in screenshots.
4. Send your snapshot
5. What happens to your data?
I use your output only to write your findings. Formspree handles the upload. I keep the files private and delete them after 30 days unless you hire me. Read my privacy policy.