Greetings, * Bharath Rupireddy (bharath.rupireddyforpostg...@gmail.com) wrote: > Thanks for the comments. Here's a new tool called pg_walcleaner which > basically deletes (optionally archiving before deletion) the unneeded > WAL files. > > Please provide your thoughts and review the patches.
Alright, I spent some more time thinking about this and contemplating what the next steps are... and I feel like the next step is basically "add a HINT when the server can't start due to being out of disk space that one should consider running pg_walcleaner" and at that point... why aren't we just, uh, doing that? This is all still quite hand-wavy, but it sure would be nice to be able to avoid downtime due to a broken archiving setup. pgbackrest has a way of doing this and while we, of course, discourage the use of that option, as it means throwing away WAL, it's an option that users have. PG could have a similar option. Basically, to archive_command/library what max_slot_wal_keep_size is for slots. That isn't to say that we shouldn't also have a tool like this, but it generally feels like we're taking a reactive approach here rather than a proactive one to addressing the root issue. Thanks, Stephen
signature.asc
Description: PGP signature
