Backups for Postgres that don’t suck

PostgreSQL is awesome in many, many ways. One of these ways is in its use of a write-ahead log, or WAL, that enables:

  • Atomicity
  • Durability
  • Replication (that isn’t insane, like MySQL’s)
  • Backups
  • And much much more! </televisionSalesman>

We’re interested in backups today, because textual dumps for backups (the lowest common denominator for mysql and pgsql) puts a lot of load on the server and tends to be very slow.

We started looking into something like mylvmbackup for postgres, but then discovered that there was no need – it’s already built in!

We’ve made a easy guide to trying it out for yourself. It’s fairly detailed and hands-on, so we’ve split things out to a separate page:

Better PostgreSQL backups with WAL archiving

If you’re a Postgres user, we’d love to know what you think. If you’re still using MySQL, why not make the switch to greener pastures? 😀