pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedMemory exhausted in AllocSetAlloc
3+ messages / 2 participants
[nested] [flat]
* Memory exhausted in AllocSetAlloc
@ 2004-09-12 02:41 C. Bensend <benny@bennyvision.com>
2004-09-12 05:43 ` Re: Memory exhausted in AllocSetAlloc Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: C. Bensend @ 2004-09-12 02:41 UTC (permalink / raw)
To: pgsql-admin
Hey folks,
I'm running 7.3.5 on an OpenBSD 3.5-STABLE machine, with 512M of RAM.
I'm running VACUUM ANALYZE every hour, with a VACUUM FULL once per night
before backups.
I'm trying to speed up the VACCUMs, so I tried bumping up vacuum_mem
in postgresql.conf from the default to 64M. This resulted in:
ERROR: Memory exhausted in AllocSetAlloc(somenumber)
(where somenumber was not written down by me, sorry)
I understand what happened, but not exactly why - this machine is
running with over 300M of RAM unused. Bumping this value down to 16M
works fine. But why does it hit a memory exhausted error at 64M?
Please let me know if this belongs on pgsql-performance - I'm getting
an actual error, so I'm hoping this is the right place. If not, I'll
join the other and post there.
Thanks much!
Benny
--
Funniest spam subject: "The mighty cucumber lives again!"
-- Received Aug 31, 2004
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Memory exhausted in AllocSetAlloc
2004-09-12 02:41 Memory exhausted in AllocSetAlloc C. Bensend <benny@bennyvision.com>
@ 2004-09-12 05:43 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-09-12 16:55 ` Re: Memory exhausted in AllocSetAlloc C. Bensend <benny@bennyvision.com>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2004-09-12 05:43 UTC (permalink / raw)
To: C. Bensend <benny@bennyvision.com>; +Cc: pgsql-admin
"C. Bensend" <benny@bennyvision.com> writes:
> I understand what happened, but not exactly why - this machine is
> running with over 300M of RAM unused. Bumping this value down to 16M
> works fine. But why does it hit a memory exhausted error at 64M?
Maybe it's exceeding a ulimit setting?
You might want to watch it with "top" and see what size the process
actually gets to before failing. I'm not sure how accurate the
vacuum_mem throttle is ...
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Memory exhausted in AllocSetAlloc
2004-09-12 02:41 Memory exhausted in AllocSetAlloc C. Bensend <benny@bennyvision.com>
2004-09-12 05:43 ` Re: Memory exhausted in AllocSetAlloc Tom Lane <tgl@sss.pgh.pa.us>
@ 2004-09-12 16:55 ` C. Bensend <benny@bennyvision.com>
0 siblings, 0 replies; 3+ messages in thread
From: C. Bensend @ 2004-09-12 16:55 UTC (permalink / raw)
To: pgsql-admin
> Maybe it's exceeding a ulimit setting?
Bingo.
> You might want to watch it with "top" and see what size the process
> actually gets to before failing. I'm not sure how accurate the
> vacuum_mem throttle is ...
It failed immediately upon invocation of vacuumdb.
I did find the problem and I feel like an idiot. For some reason
the PostgreSQL user's login class didn't get changed from the default
on this host. So, it had all kinds of limits set that were too low.
I changed that and voila!
I'm now running with 64M and my vacuums are much faster. Thanks so
much!
Benny
--
Funniest spam subject: "The mighty cucumber lives again!"
-- Received Aug 31, 2004
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2004-09-12 16:55 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-09-12 02:41 Memory exhausted in AllocSetAlloc C. Bensend <benny@bennyvision.com>
2004-09-12 05:43 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-09-12 16:55 ` C. Bensend <benny@bennyvision.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox