Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary

От

Euler Taveira

Тема

Дата

23 декабря 2021 г. в 14:52:42

Msg-id

66f58359-6241-47fd-bf25-4d105a00523c@www.fastmail.com

обсуждение

Ответ на

pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary (Bharath Rupireddy)

Список

pgsql-hackers

Дерево обсуждения

pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> 23 декабря 2021 г. в 12:58:46

Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary "Euler Taveira" <euler@eulerto.com> 23 декабря 2021 г. в 14:52:42

Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary Stephen Frost <sfrost@snowman.net> 29 декабря 2021 г. в 13:57:10

Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> 29 декабря 2021 г. в 14:36:26

pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary) Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> 18 апреля 2022 г. в 04:29:12

Re: pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary) Stephen Frost <sfrost@snowman.net> 18 апреля 2022 г. в 14:11:05

Re: pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary) Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> 18 апреля 2022 г. в 15:05:49

Re: pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary) Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> 22 апреля 2022 г. в 13:37:16

Re: pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary) Peter Eisentraut <peter.eisentraut@enterprisedb.com> 30 июня 2022 г. в 12:03:52

Re: pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary) Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> 8 июля 2022 г. в 16:33:49

Re: pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary) Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> 29 апреля 2022 г. в 12:08:51

Re: pg_walcleaner - new tool to detect, archive and delete the unneeded wal files (was Re: pg_archivecleanup - add the ability to detect, archive and delete the unneeded wal files on the primary) David Steele <david@pgmasters.net> 3 мая 2022 г. в 21:47:21

On Thu, Dec 23, 2021, at 9:58 AM, Bharath Rupireddy wrote:

pg_archivecleanup currently takes a WAL file name as input to delete
the WAL files prior to it [1]. As suggested by Satya (cc-ed) in
pg_replslotdata thread [2], can we enhance the pg_archivecleanup to
automatically detect the last checkpoint (from control file) LSN,
calculate the lowest restart_lsn required by the replication slots, if
any (by reading the replication slot info from pg_logical directory),
archive the unneeded (an archive_command similar to that of the one
provided in the server config can be provided as an input) WAL files
before finally deleting them? Making pg_archivecleanup tool as an
end-to-end solution will help greatly in disk full situations because
of WAL files growth (inactive replication slots, archive command
failures, infrequent checkpoint etc.).