From: Tom Lane <tgl@sss.pgh.pa.us>
To: 两个孩子的爹 <1726002692@qq.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.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: Fri, 28 Jan 2022 11:15:32 -0500
Message-ID: <2772241.1643386532@sss.pgh.pa.us> (raw)
In-Reply-To: <tencent_455C88A54F4AFB73D3824A2558585F911209@qq.com>
References: <17382-9b238ae4286aef7d@postgresql.org>
<2441394.1643210985@sss.pgh.pa.us>
<tencent_455C88A54F4AFB73D3824A2558585F911209@qq.com>
"=?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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, 1726002692@qq.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
In-Reply-To: <2772241.1643386532@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox