| From: | Sean Dillon <sean(at)dillonsoftware(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | excessive WAL activity |
| Date: | 2013-06-19 23:22:59 |
| Message-ID: | 3F2CE3AE-231C-4B80-A48D-3ABC9C8CE6C7@dillonsoftware.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Just turned on WAL archiving to an S3 bucket for a small database - total size of perhaps 2-4G. After turning on achiving, we're seeing WAL logs written to S3 at the rate of about 1G every 3 minutes. That seems completely unreasonable given usage of the db. I can even see that nearly nothing is happening with this:
select datname, usename, procpid, client_addr, waiting, query_start, current_query from pg_stat_activity;
Nearly every time I run that, all 20 connections have current_query = '<IDLE>'. Does current_query include inserts, updates, and deletes or just select statements?
Any ideas what to look for or how to solve this?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rural Hunter | 2013-06-20 01:38:19 | Re: Why sequence grant is separated from table? |
| Previous Message | Marcos Cano | 2013-06-19 20:21:48 | Re: pg_upgrade issue |