Postgres Pro
Downloads
Home   >   mailing lists

Thread: [pgadmin-support] VACUUM FULL Error

[pgadmin-support] VACUUM FULL Error

From
"Hayes, Patrick"
Date:

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

 

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.

Thank you in advance for any support you can provide

 

Patrick Hayes

 

Re: [pgadmin-support] VACUUM FULL Error

From
Melvin Davidson
Date:
Patrick,

Three things.
1. I am not PgAdmin support.
2. This message should actually be addressed to pgsql-general@postgresql.org
3. Support for version 8.1 ended November 2010

I suggest your best course of action is to upgrade to a recent supported version (9.5 or 9.6).

In the meantime, it looks like you need to increase your shared_buffers parameter in your
postgresql.conf and restart the postgres server.


Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.
www.youtube.com/unusedhero/videos
Folk Alley - All Folk - 24 Hours a day
www.folkalley.com



From: "Hayes, Patrick" <Patrick.Hayes@stryker.com>
To: "pgadmin-support@postgresql.org" <pgadmin-support@postgresql.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
 
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.
Thank you in advance for any support you can provide
 
Patrick Hayes
 


Attachment

Re: [pgadmin-support] VACUUM FULL Error

From
Raymond O'Donnell
Date:
On 30/12/16 14:11, Melvin Davidson wrote:
> *2. This message should actually be addressed to
> pgsql-general@postgresql.org <http://pgsql-general@postgresql.org/>
> *
> *3. Support for version 8.1 ended November 2010*
> *   https://www.postgresql.org/support/versioning/

<snip>

>
> ------------------------------------------------------------------------
> *From:* "Hayes, Patrick" <Patrick.Hayes@stryker.com>
> *To:* "pgadmin-support@postgresql.org" <pgadmin-support@postgresql.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@iol.ie