On Wed, 2005-06-29 at 16:40 -0400, Charles Swiger wrote:
> On Jun 29, 2005, at 4:12 PM, Sven Willenberger wrote:
> [ ... ]
> > Something I have noticed,
> > when the memory error occurs during the psql session (after a failed
> > vacuumdb attempt) the memory stays at 600+MB in top (under size) unti
On Jun 29, 2005, at 4:12 PM, Sven Willenberger wrote:
[ ... ]
Something I have noticed,
when the memory error occurs during the psql session (after a failed
vacuumdb attempt) the memory stays at 600+MB in top (under size) until
the psql session is closed -- that may just be the way top reports it
On Wed, 2005-06-29 at 14:59 -0400, Vivek Khera wrote:
> On Jun 29, 2005, at 9:01 AM, Sven Willenberger wrote:
>
> > Unix user root (and any psql superuser) the vacuum runs fine. It is
> > when
> > the unix user is non-root (e.g. su -l pgsql -c "vacuumdb -a -z") that
> > this memory error occurs.
Sven Willenberger <[EMAIL PROTECTED]> writes:
> Again, if I log in as myself and try to run
> the command vaccumdb -a -z it fails; if I su to root and repeat it works
> fine. I am trying to narrow this down to a PostgreSQL issue vs FreeBSD
> issue.
That's really weird, b
On Wed, 2005-06-29 at 09:43 -0400, Douglas McNaught wrote:
> Sven Willenberger <[EMAIL PROTECTED]> writes:
>
> > FreeBSD 5.4-Release
> > PostgreSQL 8.0.3
> >
> > I noticed that the nightly cron consisting of a vacuumdb was failing due
> > to "unable to allocate memory". I do have maintenance_mem s
Sven Willenberger <[EMAIL PROTECTED]> writes:
> FreeBSD 5.4-Release
> PostgreSQL 8.0.3
>
> I noticed that the nightly cron consisting of a vacuumdb was failing due
> to "unable to allocate memory". I do have maintenance_mem set at 512MB,
> and the /boot/loader.conf file sets the max datasize to 1G
