Patrick, Three things.1. I am not PgAdmin support. 2. This message should actually be addressed to pgsql-gene...@postgresql.org 3. Support for version 8.1 ended November 2010 https://www.postgresql.org/support/versioning/
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 yourpostgresql.conf and restart the postgres server. https://www.postgresql.org/message-id/4057e37d0fad0814281017dc6c211c00.squir...@sq.gransy.com 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.ha...@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 <!--#yiv5475902005 _filtered #yiv5475902005 {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv5475902005 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv5475902005 {font-family:"Arial Black";panose-1:2 11 10 4 2 1 2 2 2 4;}#yiv5475902005 #yiv5475902005 p.yiv5475902005MsoNormal, #yiv5475902005 li.yiv5475902005MsoNormal, #yiv5475902005 div.yiv5475902005MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Calibri", sans-serif;}#yiv5475902005 a:link, #yiv5475902005 span.yiv5475902005MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv5475902005 a:visited, #yiv5475902005 span.yiv5475902005MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv5475902005 span.yiv5475902005EmailStyle17 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv5475902005 span.yiv5475902005EmailStyle18 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5475902005 span.yiv5475902005EmailStyle19 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5475902005 span.yiv5475902005EmailStyle20 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv5475902005 span.yiv5475902005EmailStyle21 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5475902005 span.yiv5475902005EmailStyle22 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5475902005 span.yiv5475902005EmailStyle23 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv5475902005 span.yiv5475902005EmailStyle24 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5475902005 span.yiv5475902005EmailStyle25 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv5475902005 span.yiv5475902005EmailStyle26 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5475902005 span.yiv5475902005EmailStyle27 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5475902005 span.yiv5475902005EmailStyle28 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5475902005 .yiv5475902005MsoChpDefault {font-size:10.0pt;} _filtered #yiv5475902005 {margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv5475902005 div.yiv5475902005WordSection1 {}-->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 PatrickHayes
-- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
