docs: Point-in-Time Recovery covers MySQL (standalone and HA) - #1344
Open
paulocsanz wants to merge 2 commits into
Open
docs: Point-in-Time Recovery covers MySQL (standalone and HA)#1344paulocsanz wants to merge 2 commits into
paulocsanz wants to merge 2 commits into
Conversation
The PITR page described Postgres only. MySQL PITR has shipped — binlog archiving from Railway's MySQL image with daily full logical backups and a 7-day horizon, standalone and on MySQL HA (rolling enable, archiving from the writable primary, restore across primary handoffs) — so the page now covers both engines: how each archives, the enable flow (including the stock template's move onto Railway's MySQL image at the same version), the engine-neutral restore/disable/HA paragraphs, cost per engine and the MySQL equivalents of the Postgres limitations. databases/mysql.md and databases/mysql-ha.md link to it.
Growth check — AMH estimate#1344 @ Files considered:
SEO leg (Google surface)2–6.8 visits/mo AEO leg (AI assistants)1.2–3.5 visits/mo Gates
Keyword candidates for the AMH panelNew (not yet curated) deploy/hosting-intent keywords found around this content — candidates to add to the panel/Gauge:
Caveats & verification stamps
How to go deeperAsk an agent with the Ahrefs cost: 3108 API units · How AMH is calculated |
|
🚅 Deployed to the docs-pr-1344 environment in 🪄 *.railway.com
6 services not affected by this PR
|
railway-app
Bot
temporarily deployed
to
*.railway.com / docs-pr-1344
September 7, 2026 16:12
Destroyed
Binlog events are stamped to the second and the restore stops at the first event at or after the target's second, so a MySQL restore yields the state as of the start of the chosen second. Said once where the archive's timing is described and once in the engine differences list.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The Point-in-Time Recovery page described Postgres only. MySQL PITR has shipped — standalone (
mysql-pitroverlay, binlog archiving from Railway's MySQL image) and MySQL HA (rolling enable, archiving from the writable primary, restore across primary handoffs) — so the page now covers both engines:mysqlimage is moved onto Railway's MySQL image at the same version, the template start command is cleared, a customized start command has to be removed first.databases/mysql.mdgains a Point-in-time recovery bullet under Backups.The CLI section stays Postgres-only:
railway mysql pitris in flight (railwayapp/cli#1144) and not released.Source of truth
Retention, cadence and rotation values are the image's defaults (
BINLOG_RETENTION_DAYS=7,BINLOG_FULL_BACKUP_INTERVAL_SECONDS=86400,BINLOG_ROTATE_INTERVAL_SECONDS=60in mysql-ha'sconfig.rs); the transition rule ismysqlPitrOfficialTransition.tsin mono; the fail-closed restore isrestore.rs's gap/GTID checks.