X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D4979D1B19C for ; Fri, 25 Jun 2004 13:42:42 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 01633-03 for ; Fri, 25 Jun 2004 16:42:33 +0000 (GMT) Received: from web60305.mail.yahoo.com (web60305.mail.yahoo.com [216.109.118.116]) by svr1.postgresql.org (Postfix) with SMTP id 3D420D1B7C9 for ; Fri, 25 Jun 2004 13:42:31 -0300 (ADT) Message-ID: <20040625164231.34710.qmail@web60305.mail.yahoo.com> Received: from [200.138.220.128] by web60305.mail.yahoo.com via HTTP; Fri, 25 Jun 2004 09:42:31 PDT Date: Fri, 25 Jun 2004 09:42:31 -0700 (PDT) From: Carlos Benkendorf Subject: Vacuum x Vacuum full To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1297441489-1088181751=:34421" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=HTML_MESSAGE, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200406/336 X-Sequence-Number: 13996 --0-1297441489-1088181751=:34421 Content-Type: text/plain; charset=us-ascii I would like to know if space disk is free to the Operational System during a standard vacuum (without the full option)? I found in section "21.1.1 Recovering disk space" of Postgresql 7.4.2 manual something about it. "The standard form of VACUUM is best used with the goal of maintaining a fairly level steady-state usage of disk space.The standard form finds old row versions and makes their space available for re-use within the table, but it does not try very hard to shorten the table file and return disk space to the operating system. " Even so it is not clear. They say the space will be available for re-use within the table so I realized the space will not be available to the operational system. But they also say the command "does not try very hard to shorten the table file and return disk space to the operating system" what means to me that it could sometimes free space to the operating system. I could not clear my doubt. Will the standard form, free disk space to the operational system or not? I did some tests and discovered that the standard form frees disk space to the operational system. But if the standard form already frees it why the full form will do different? Thanks in advance! --------------------------------- Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. --0-1297441489-1088181751=:34421 Content-Type: text/html; charset=us-ascii
I would like to know if space disk is free to the Operational System
during a standard vacuum (without the full option)?
 
I found in section "21.1.1 Recovering disk space" of Postgresql 7.4.2 manual
something about it.

"The standard form of VACUUM is best used with the goal of maintaining a fairly level steady-state usage of disk space.The standard form finds old row versions and makes their space available for re-use within the table, but it does not try very hard to shorten the table file and return disk space to the operating system. "
 
Even so it is not clear. They say the space will be available for re-use
within the table so I realized the space will not be available to
the operational system. But they also say the command "does not try very
hard to shorten the table file and return disk space to the operating
system" what means to me that it could sometimes free space to the
operating system.
 
I could not clear my doubt. Will the standard form, free disk space to the
operational system or not?
 
I did some tests and discovered that the standard form frees disk space
to the operational system. But if the standard form already frees it why the full form
will do different?
Thanks in advance!


Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone. --0-1297441489-1088181751=:34421--