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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the
Дата
Msg-id 2772241.1643386532@sss.pgh.pa.us
обсуждение исходный текст
Ответ на 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>)
Список pgsql-bugs
Дерево обсуждения 
"=?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 по дате отправления:

Предыдущее
От: Dmitry Koval
Дата:
Сообщение: Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end
Следующее
От: "Drouvot, Bertrand"
Дата:
Сообщение: snapshot recovery conflict despite hot_standby_feedback set to on