> 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 f
"C. Bensend" <[EMAIL PROTECTED]> 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 mi
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 r
We had problems with postgres when using ODBC (in Acess97), this message
comes out on the console:
FATAL 1: Memory exhausted in AllocSetAlloc()
pq_recvbuf: unexpected EOF on client connection
Is there a tweak we can do? This is the 6.4 release.
Thanks,
Brian
--
[EMAIL PROTECTED]
http://www.baq
