Re: VACUUM FULL Error

On 30/12/16 14:11, Melvin Davidson wrote:
> *2. This message should actually be addressed to
> pgsql-general(at)postgresql(dot)org <http://pgsql-general(at)postgresql(dot)org/>
> *
> *3. Support for version 8.1 ended November 2010*
> * https://www.postgresql.org/support/versioning/

<snip>

>
> ------------------------------------------------------------------------
> *From:* "Hayes, Patrick" <Patrick(dot)Hayes(at)stryker(dot)com>
> *To:* "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org>
> *Sent:* Thursday, December 29, 2016 5:52 AM
> *Subject:* [pgadmin-support] VACUUM FULL Error
>
> Hi pgAdmin support,
>
> Recently truncated tables in Postgre SQL DB and now unable to free up
> disk space on server with the VACUUM FULL command.
> The DB is 1.91TBytes in size.
> Server is running Win 2008 R2 Standard Operating System.
> Postgre SQL is version 8.1

Hi there,

As Melvin pointed out, you'll get better answers on the pgsql-general
mailing list; this list is for pgAdmin, which is a PG administration tool.

Also, as Melvin also correctly pointed out, 8.1 is incredibly ancient;
the current version is 9.6.

> Error message reads as follows:
> /ERROR: out of memory/
> /DETAIL: Failed on request of size 134217728./
>
> Adding memory to server does not seem to make any difference.
> Re-starting the server makes no difference. The VACUUM command always
> ends in the same record 134217728.
> Is there any way to selectively VACUUM tables – divide and conquer approach.

Yes, there is, in current versions anyway:

https://www.postgresql.org/docs/9.6/static/sql-vacuum.html

Hope this helps,

Ray.

--
Raymond O'Donnell :: Galway :: Ireland
rod(at)iol(dot)ie