Re: BUG #4513: VACUUM FULL fails with "out of memory" error

"Alexey Bashtanov" <bashtanov@imap.cc> writes:

> The following bug has been logged online:
>
> Bug reference:      4513
> Logged by:          Alexey Bashtanov
> Email address:      bashtanov@imap.cc
> PostgreSQL version: 8.3.1
> Operating system:   Red Hat Linux  2.6.20-1.2320.fc5smp i686
> Description:        VACUUM FULL fails with "out of memory" error

Are you sure this is 8.3.1 and not 8.3.0? There is a bug fixed in 8.3.1 which
sounds a lot like this:

   Another VACUUM FULL bug introduced in 8.3 could result in a crash or
   out-of-memory report when dealing with pages containing no live tuples.

> Here's the part of serverlog:
> ==========
> TopMemoryContext: 49416 total in 6 blocks; 8776 free (46 chunks); 40640
> used
>   TopTransactionContext: 2986336304 total in 367 blocks; 192312 free (1088
> chunks); 2986143992 used

It does look like you have a memory leak in VACUUM FULL. There have been three
memory leaks fixed in bug-fix releases since 8.3.1 but none should be related
to VACUUM FULL.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's Slony Replication support!