Comments on: PostgreSQL Upgrade Using pg_dump/pg_restore https://www.percona.com/blog/postgresql-upgrade-using-pg_dump-pg_restore/ Tue, 26 Dec 2023 19:00:33 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Edward Ribeiro https://www.percona.com/blog/postgresql-upgrade-using-pg_dump-pg_restore/#comment-10970590 Mon, 08 Apr 2019 18:28:27 +0000 https://www.percona.com/blog/?p=56089#comment-10970590 On the rush, I didn’t congratulate you guys for the nice article. Thanks for sharing!

]]> By: Jobin Augustine https://www.percona.com/blog/postgresql-upgrade-using-pg_dump-pg_restore/#comment-10970567 Fri, 05 Apr 2019 08:14:39 +0000 https://www.percona.com/blog/?p=56089#comment-10970567 Thank you Edward for this feedback.

]]> By: Edward Ribeiro https://www.percona.com/blog/postgresql-upgrade-using-pg_dump-pg_restore/#comment-10970556 Thu, 04 Apr 2019 16:52:20 +0000 https://www.percona.com/blog/?p=56089#comment-10970556 “A dump taken in plain text format may be slightly larger in size when compared to a custom format dump.”

FYI, a dump of one of my clients’ databases has the following sizes:

text format: 131MB
custom format: 29M

Usually, I see text format being between 4x to 7x larger (or 100x larger on extreme cases) than custom format for a database with lots of tables and rows. Nevertheless, text formats that size make a difference when restoring because it takes a much longer time to replay all the commands.

]]>