From: Tom Lane <tgl@sss.pgh.pa.us>
To: 1726002692@qq.com
cc: 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: <17382-9b238ae4286aef7d@postgresql.org>
References: <17382-9b238ae4286aef7d@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 26 Jan 2022 08:25:20 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2441393.1643210985.1@sss.pgh.pa.us>
Date: Wed, 26 Jan 2022 10:29:45 -0500
Message-ID: <2441394.1643210985@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2441394.1643210985%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> When vacuum full or vacuumdb - F is executed, a large number of empty files
> will be generated in the database. These files have never been deleted.
> Each execution of vacuum full or vacuudb - F will produce a large number of
> empty files.These empty files will not be deleted until the database is
> restarted.
> Is this a bug?

It might be if you could tell us how to reproduce it --- I see no
such behavior here.

In general, PG uses numerically-named files for table contents,
but they should always appear in subdirectories of $PGDATA, never
in the directory's top level.  So I have no idea what those are
or what put them there.  Perhaps you are using some unusual
extension or custom C code that creates them?

			regards, tom lane