| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | wambacher <wnordmann(at)gmx(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: autovacuum worker running amok - and me too ;) |
| Date: | 2015-03-03 23:17:01 |
| Message-ID: | 1760.1425424621@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
wambacher <wnordmann(at)gmx(dot)de> writes:
> My system has 24GB of real memory but after some hours one autovacuum worker
> is using 80-90% of memory, the OOM-Killer (out of memory killer) kills the
> process with kill -9 and the postgresql-server is restarting because of that
> problem.
> i changed the base configuration to use very small buffers, restartetd the
> server twice but the problem still exists.
> i think, it's allways the same table and that table is huge: 111GB data and
> 3 Indices with 4GB, 128 GB and 12 GB. It's the table planet_osm_ways from
> openstreetmap. maybe that helps.
Maybe you could reduce the statistics targets for that table.
I think we've heard that the analyze functions for PostGIS data types are
memory hogs, too --- maybe it's worth inquiring about that on the postgis
mailing lists.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wambacher | 2015-03-03 23:38:54 | Re: autovacuum worker running amok - and me too ;) |
| Previous Message | wambacher | 2015-03-03 23:06:46 | autovacuum worker running amok - and me too ;) |