Skip to content

v6.0.2 - #158

Merged
bfren merged 8 commits into
mainfrom
v6.0.2
Nov 10, 2026
Merged

v6.0.2#158
bfren merged 8 commits into
mainfrom
v6.0.2

Conversation

@bfren

@bfren bfren commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Merging branch to create v6.0.2.

bfren and others added 8 commits November 6, 2026 12:48
Move the files in /data to /backup/<yyyyMMddHHmm>-before-restore instead of
deleting them. psql exits 0 when statements fail, so a bad dump could leave
a partial cluster with no copy of the old data. The folder expires with the
other backups.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
So a list copied from bfren/mariadb works here too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Name the before-restore folder down to the second and stop if it already
exists - mv overwrites or skips files in an existing folder without an
error, so two restores in the same minute mixed the saved copy with the
second cluster. Also stop if any files are left in /data after the move
(e.g. the disk is full).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Restores delete /data again, as in v6.0.1. Moving the data to /backup
needed room there for a full copy, and a restore stopped part-way (with
PostgreSQL down) when there was not enough - a failure the release before
did not have.

This reverts commits 7314ec0 and c409da7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A restore deletes the current data before loading the dump, so the README
now says to run pg-dump (or copy /data) first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bfren
bfren merged commit 07872c6 into main Nov 10, 2026
21 checks passed
@bfren
bfren deleted the v6.0.2 branch November 10, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant