Autovacuum - default:
#autovacuum = on # Enable autovacuum subprocess? 'on'
#log_autovacuum_min_duration = -1 # -1 disables, 0 logs all actions and
#autovacuum_max_workers = 3 # max number of autovacuum subprocesses
#autovacuum_naptime = 1min # time between autovacuum runs
autovacuum_vacuum_threshold = 500 # min number of row updates before
autovacuum_analyze_threshold = 500 # min number of row updates before
#autovacuum_vacuum_scale_factor = 0.2 # fraction of table size before vacuum
#autovacuum_analyze_scale_factor = 0.1 # fraction of table size before analyze
#autovacuum_freeze_max_age = 200000000 # maximum XID age before forced vacuum
#autovacuum_vacuum_cost_delay = 20ms # default vacuum cost delay for
# autovacuum, in milliseconds;
#autovacuum_vacuum_cost_limit = -1 # default vacuum cost limit for
# autovacuum, -1 means use
Regards,
Steve
----------------------------------------
> From: ilya.kosmodemiansky@postgresql-consulting.com
> Date: Wed, 18 Mar 2015 13:17:14 +0100
> Subject: Re: [PERFORM] Very slow checkpoints
> To: steven.jones1201@outlook.com
> CC: pgsql-performance@postgresql.org
>
> On Wed, Mar 18, 2015 at 12:21 PM, Steven Jones
> <steven.jones1201@outlook.com> wrote:
>> - typical DW - relatively constant periodic data loads - i.e. heavy write
>> - we receive large CSV files ~ 5-10Gb every 15 minutes spread out across
>> 5-7 minutes
>> - DB size is ~2.5Tb; rotating load of 30 days keeps the database stable
>
> And an important addition: how your autovacuum is configured?
>
>
> --
> Ilya Kosmodemiansky,
>
> PostgreSQL-Consulting.com
> tel. +14084142500
> cell. +4915144336040
> ik@postgresql-consulting.com
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance