Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
Date
Msg-id 2772241.1643386532@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the  ("两个孩子的爹" <1726002692@qq.com>)
List pgsql-bugs
Tree view 
"=?gb18030?B?wb249rqi19O1xLX5?=" <1726002692@qq.com> writes:
> Sorry, it's my fault. The empty files generated by "vacuumdb - f " is located under the $pgdata / base / 99522
directory

Oh, if they are under the database's subdirectory then it's not so
surprising.  VACUUM FULL (or, actually, any table deletion or rewrite)
leaves behind an empty "tombstone" file that is just there to prevent
re-use of that table number for the moment.  It'll go away at the next
checkpoint.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Dmitry Koval
Date:
Subject: Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end
Next
From: "Drouvot, Bertrand"
Date:
Subject: snapshot recovery conflict despite hot_standby_feedback set to on