Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL's vacuumdb fails to allocate memory for

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sven Willenberger <sven(at)dmv(dot)com>
Cc: Douglas McNaught <doug(at)mcnaught(dot)org>,pgsql-general(at)postgresql(dot)org, stable(at)freebsd(dot)org
Subject: Re: PostgreSQL's vacuumdb fails to allocate memory for
Date: 2005-06-29 15:21:41
Message-ID: 9731.1120058501@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Sven Willenberger <sven(at)dmv(dot)com> writes:
> ERROR:  out of memory
> DETAIL:  Failed on request of size 536870910.

That's a server-side failure ...

> 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 fairly hard to believe, assuming that you are talking to the same
server in both cases (I have seen trouble reports that turned out to be
because the complainant was accidentally using two different servers...)
The ulimit the backend is running under couldn't change depending on
where the client is su'd to.

Is it possible that you've got per-user configuration settings that
affect this, like a different maintenance_mem value for the root user?

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: Douglas McNaughtDate: 2005-06-29 15:29:05
Subject: Re: how to use pg_dump and then restored onto development server
Previous:From: Tom LaneDate: 2005-06-29 15:16:50
Subject: Re: CVS Build - No Doc

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group