4 ms·
(supabase ceo) To give context, Val Town have a particularly write-heavy setup, storing a lot of json strings. The nightly backups were causing write-contentio
by kiwicopple 3y ago
(supabase ceo)
To give context, Val Town have a particularly write-heavy setup, storing a lot of json strings. The nightly backups were causing write-contention, even at their relatively small size. We didn’t detect errors because they were application-level. We should have moved them to PITR as soon as they mentioned it since the timing was so obviously coinciding with backups. We’re investigating moving everyone to PITR (including the free tier). At the very least, we’ll add more control for backups - allowing users to change the maintenance window, or possibly disabling backups completely if they are managing it themselves.
- aeyes 3y agohow does a backup cause write contention? are you backing up to the same disk? also why are backups using pg_dump? that’s not a backup.
- nfm 3y agohttps://www.postgresql.org/docs/current/app-pgdump.html https://www.postgresql.org/docs/current/app-pgdump.html > pg_dump is a utility for backing up a PostgreSQL database. It makes consistent backups even if the database is being used concurrently.
- paulryanrogers 3y agoPossibly MVCC keeping a snapshot so the whole dump is consistent.