4 ms·
Ouch that will make migrating anything over a few hundred gigs almost impossible. Our postgres db is about 2TB and pgdump stopped being viable a long time ago.
by fourseventy 3y ago
Ouch that will make migrating anything over a few hundred gigs almost impossible. Our postgres db is about 2TB and pgdump stopped being viable a long time ago.
- BuildTheRobots 3y ago> Our postgres db is about 2TB and pgdump stopped being viable a long time ago. Due to the time it takes to export, or because it can't handle a database of that size at all?
- a2800276 3y agoI'd assume they mean time to export, while 2TB is a substantial database, it's not pushing postgres limits.
- redeeman 3y agoyou can use pg_basebackup to kickstart a replication slave. You can then just just down old and use new with ~1sec downtime. If you need to upgrade postgres at same time, you can then cascade to another one slave on same "new" host for safety, and pg_upgrade on that one. This will result in a bit more downtime, but also upgrading postgres version.