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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 两个孩子的爹 <1726002692(at)qq(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
Date: 2022-01-28 16:15:32
Message-ID: 2772241.1643386532@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"=?gb18030?B?wb249rqi19O1xLX5?=" <1726002692(at)qq(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Drouvot, Bertrand 2022-01-28 16:17:20 snapshot recovery conflict despite hot_standby_feedback set to on
Previous Message Dmitry Koval 2022-01-28 15:26:08 Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end