From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "bricklen *EXTERN*" <bricklen(at)gmail(dot)com>, Sean Dillon <sean(at)dillonsoftware(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: excessive WAL activity |
Date: | 2013-06-21 07:54:16 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17BB4E3B@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
bricklen wrote:
> On Wed, Jun 19, 2013 at 4:22 PM, Sean Dillon <sean(at)dillonsoftware(dot)com> wrote:
>> 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?
>
> Can you show the results from:
>
> SELECT name, current_setting(name), source
> FROM pg_settings
> WHERE source NOT IN ('default', 'override')
> UNION ALL
> SELECT 'version' as name, version(), null;
>
>
> Perhaps there is a setting there (like archive_timeout) which could lead to an answer. In your
> $PGDATA/pg_xlog directory, look at the timestamps of the WAL segments, are there lots of files
> generated per minute?
Also, it might be good to check how much is really going on.
Try log_statement=all and see how much gets logged.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2013-06-21 08:03:04 | Re: PostgreSQL 8.4 - permissions for newly created tables? |
Previous Message | Marcos Cano | 2013-06-20 18:27:20 | Re: PG_UPGRADE major issue |