PG_ARCHIVECLEANUP(1)
π PG_ARCHIVECLEANUP(1) π
okay bestie, welcome to the manual page for pg_archivecleanup β the PostgreSQL 16.15 documentation's very own WAL-archive janitor, and honestly? it's giving "quietly does the most important job at the party" energy. π
β¨ NAME β¨
pg_archivecleanup β clean up PostgreSQL WAL archive files. yep, that's it, that's the whole vibe. she cleans. she archives. she slays. π
β¨ SYNOPSIS β¨
pg_archivecleanup [option...] archivelocation oldestkeptwalfile
β¨ DESCRIPTION β¨
so pg_archivecleanup is literally designed to be used as an archive_cleanup_command β like, that's her whole main character arc β to clean up WAL file archives when you're running as a standby server (peep Section 27.2 if you wanna go deeper π). but also? she can absolutely be used as a standalone program to clean WAL file archives. versatile icon. π
to configure a standby server to use pg_archivecleanup, drop this into its postgresql.conf configuration file:
archive_cleanup_command = 'pg_archivecleanup archivelocation %r'
where archivelocation is the directory from which WAL segment files should be removed. ποΈβ¨
when she's used within archive_cleanup_command, all WAL files logically preceding the value of the %r argument will be removed from archivelocation. the way this minimizes the number of files that need to be retained while preserving crash-restart capability?? obsessed. π«Ά
β οΈ okay important vibe check: use of this parameter is appropriate if thearchivelocationis a transient staging area for this particular standby server β but not when thearchivelocationis intended as a long-term WAL archive area, or when multiple standby servers are recovering from the same archive location. pls don't do her dirty like that. π
when used as a standalone program, all WAL files logically preceding the oldestkeptwalfile will be removed from archivelocation. and in this mode, if you specify a .partial or .backup file name, then only the file prefix will be used as the oldestkeptwalfile. this treatment of .backup file name allows you to remove all WAL files archived prior to a specific base backup without error β no drama, no mess, just vibes. π
for example, the following example will remove all files older than WAL file name 000000010000003700000010:
pg_archivecleanup -d archive 000000010000003700000010.00000020.backup
pg_archivecleanup: keep WAL file "archive/000000010000003700000010" and later
pg_archivecleanup: removing file "archive/00000001000000370000000F"
pg_archivecleanup: removing file "archive/00000001000000370000000E"
and just so we're clear: pg_archivecleanup assumes that archivelocation is a directory readable and writable by the server-owning user. no exceptions, bestie. π
β¨ OPTIONS β¨
pg_archivecleanup accepts the following command-line arguments:
-dβ print lots of debug logging output onstderr. she's a talker and we love that for her. π£οΈ-nβ print the names of the files that would have been removed onstdout(performs a dry run). literally the "look but don't touch" of file deletion. π-V,--versionβ print thepg_archivecleanupversion and exit. identity check real quick. πͺ-xextension β provide an extension that will be stripped from all file names before deciding if they should be deleted. this is typically useful for cleaning up archives that have been compressed during storage, and therefore have had an extension added by the compression program. for example:-x .gz. ποΈβ¨-?,--helpβ show help aboutpg_archivecleanupcommand line arguments, and exit. the "wait what does this do again" button. π
β¨ ENVIRONMENT β¨
the environment variable PG_COLOR specifies whether to use color in diagnostic messages. possible values are always, auto and never. yes she has a color palette. aesthetics matter. π¨
β¨ NOTES β¨
pg_archivecleanup is designed to work with PostgreSQL 8.0 and later when used as a standalone utility, or with PostgreSQL 9.0 and later when used as an archive cleanup command. old-school compatible, no cap. β
pg_archivecleanup is written in C and has an easy-to-modify source code, with specifically designated sections to modify for your own needs. she's open, she's giving "come customize me", she's a builder. π§
β¨ EXAMPLES β¨
on Linux or Unix systems, you might use:
archive_cleanup_command = 'pg_archivecleanup -d /mnt/standby/archive %r 2>>cleanup.log'
where the archive directory is physically located on the standby server, so that the archive_command is accessing it across NFS, but the files are local to the standby. πβπΎ
this will:
- produce debugging output in
cleanup.log - remove no-longer-needed files from the archive directory
okay that's the whole page!! π source & version tea: this is PostgreSQL 16.15, dated 2026, and it's the PG_ARCHIVECLEANUP(1) page β now go forth and clean those WAL archives, bestie, you're gonna eat. π₯ππΈ
π¦ where this page comes from
- opensuse-leap 16.0: postgresql16-contrib 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16-contrib 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16-contrib 16.15-160000.1.1 Β· PostgreSQL
- opensuse-leap 16.0: postgresql16-contrib 16.15-160000.1.1 Β· PostgreSQL
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms