From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | tim truman <mitramnut(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: autovacuum out of memory errors |
Date: | 2013-09-11 19:20:16 |
Message-ID: | 1378927216.15764.YahooMailNeo@web162903.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
tim truman <mitramnut(at)gmail(dot)com> wrote:
> [ memory usage map ]
There doesn't seem to be any memory context using an unusually large amount of RAM.
> 522f9128.1151 ERROR: out of memory
> 522f9128.1151 DETAIL: Failed on request of size 336150396.
> 522f9128.1151 CONTEXT: automatic vacuum of table "client.public.product"
>
> SELECT version();
> PostgreSQL 8.4.11 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.4.real (Debian 4.4.5-8) 4.4.5, 64-bit
http://www.postgresql.org/support/versioning/
> maintenance_work_mem | 1GB
> max_connections | 1000
> shared_buffers | 11GB
> wal_buffers | 8MB
> work_mem | 8MB
> free -m
> total used free shared buffers cached
> Mem: 48396 48139 257 0 173 44771
> -/+ buffers/cache: 3194 45201
> Swap: 956 20 936
Clearly the free command was not run while the database service was
running. Can we see what that looks like when it is running and
handling roughly the same workload that has been causing problems
(including any non-database processes which have been running on
the machine during failures)?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas | 2013-09-11 19:46:58 | Re: Re: PG 9.3 complains about specified more than once ??? Those views worked in PG 9.1 + 9.2 |
Previous Message | David Johnston | 2013-09-11 19:09:13 | Re: PG 9.3 complains about specified more than once ??? Those views worked in PG 9.1 + 9.2 |