diff options
| -rw-r--r-- | doc/src/sgml/maintenance.sgml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 66356c0d012..a3800c60822 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.51 2005/11/04 23:14:00 petere Exp $ +$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.52 2005/12/07 05:35:53 momjian Exp $ --> <chapter id="maintenance"> @@ -141,11 +141,12 @@ $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.51 2005/11/04 23:14:00 pete command. The first form, known as <quote>lazy vacuum</quote> or just <command>VACUUM</command>, marks expired data in tables and indexes for future reuse; it does <emphasis>not</emphasis> attempt - to reclaim the space used by this expired data - immediately. Therefore, the table file is not shortened, and any - unused space in the file is not returned to the operating - system. This variant of <command>VACUUM</command> can be run - concurrently with normal database operations. + to reclaim the space used by this expired data unless the space is + at the end of the table and an exclusive lock can be obtained easily + on the table. Unused space at the start or middle of the file does + not result in the file being shortened and space returned to the + operating system. This variant of <command>VACUUM</command> can be + run concurrently with normal database operations. </para> <para> |