Do we want a backup of the database on Kingfisher live?

[ghost]

Tho we should be able to reload almost everything* from files on disk, it would take a while.

This came up in conversation with @kindly.

ps.* The tiny exception is explained in open-contracting/kingfisher-process#122

[jpmckinney]

Identify + implement mitigations for kingfisher-process downtime

[jpmckinney]

#86 proposes a replication server. In case of downtime, disk failure, etc., I think we'd want a 'hot' backup (one we can quickly and easily switch over to), rather than pg_dump outputs that then need to be loaded into a new/restored server. If that's correct, then we can close this in favor of #86.