| From: | Baptiste LHOSTE <blhoste(at)alaloop(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Cc: | cedric(at)2ndquadrant(dot)com, Kevin Grittner <kgrittn(at)mail(dot)com> |
| Subject: | Re: Autoanalyze of the autovacuum daemon ... |
| Date: | 2012-11-09 16:37:01 |
| Message-ID: | 1371322936.10167628.1352479021824.JavaMail.root@alaloop.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>> Please show us the output from running this query:
>>
>> http://wiki.postgresql.org/wiki/Server_Configuration
> [very reasonable settings except for a very large work_mem]
> Make sure that work_mem setting isn't driving you into swapping or
> near-zero caching. A shortage of cache space could explain this
> because it looks like about 8.5 ms for each page read. About the only
> other thing I can think to recommend is to decrease
> autovacuum_cost_delay to 10ms and see if that helps.
When I run a command htop on my server I can not see any swap issue :
Mem 4Go / 16Go
Swp 175B / 4Go
I am sorry but I do not understand we you suggest to decrease autovacuum_cost_delay to 10 ms.
We already set autovacuum_vacuum_cost_delay to 10ms for those tables.
>> 4 * 300 Go Raid 0
> You do realize that if any of those four drives fail you will need to
> use your backup, right?
Yes, we do. We already used our backup when we changed some old servers.
Regards, Baptiste.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pat Heuvel | 2012-11-11 00:27:34 | No databases visible on pg 8.3 server |
| Previous Message | Kevin Grittner | 2012-11-09 15:59:57 | Re: Autoanalyze of the autovacuum daemon ... |