Comments on: Backup and Restore a PostgreSQL Cluster With Multiple Tablespaces Using pg_basebackup https://www.percona.com/blog/backup-restore-postgresql-cluster-multiple-tablespaces-using-pg_basebackup/ Thu, 14 Dec 2023 01:22:21 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Shashank R https://www.percona.com/blog/backup-restore-postgresql-cluster-multiple-tablespaces-using-pg_basebackup/#comment-10972168 Wed, 29 Apr 2020 12:01:23 +0000 https://www.percona.com/blog/?p=54438#comment-10972168 Hi Avinash,

I am new to Postgresql. In our project we are trying to migrate to Postgresql.

When there is a requirement to LOAD huge volume of data into a table, usual process followed in Mainframe – DB2 is as mentioned below

• Set Quiesce point or take image copy of the tablespace (this is nothing but a backup/restore point if in case there is issue with loading the data)
• Load table
• Repair tablespace – This is to check copy pending status and Check data
• Reorg and Runstats Indexes in the tablespace – This is to ensure that the indexes are rebuilt post the mass load.

If the load volume is low or confined to few hundreds of records not all of these steps are performed. The only reason for following the above process is for performance.

Kindly let me know for Postgres what is the process followed in general, I believe not all the above steps are required. Please clarify.

Thanks,

Shashank R.

]]>