In this post, I am sharing few important points which should perform before populating new database in PostgreSQL.

Populating a new database means, creating another copy of the database on a different server or different location. In the ETL process, populating database is widespread requirements and people are populating the database for various purpose like testing, backup, validation.

But before actual migration, we should follow few steps which also help us to improve the performance of migration activity.

Follow the below steps in the source database (Before migration):

Disable all DDL/DML triggers

Use COPY Command

Instead of creating multiple COPY command, you can create a JSON manifest file and can build only one COPY Command for all the tables

Disable Indexes

Disable Foreign Key Constraints

Disable logs of database

Disable Replication (If any)

Increase maintenance_work_mem

Increase max_wal_size

Follow the below steps in destination database (After migration):

Disable auto-commit

Disable logs of database

Increase maintenance_work_mem

Increase max_wal_size

Check the current value of sequences, and if it is 0 then reset by appropriate value

Check the database character set, default timezone, tablespaces

Enable Indexes, Foreign Keys

Run ANALYZE on database

One of the Important news for Database Community.
The UBER taxi number one company switched from PostgreSQL to MySQL.

There are a few major reasons behind for this migration.
As per the official document of UBER, they were facing a few notable issues with the PostgreSQL.

• Inefficient architecture for writes
• Inefficient data replication
• Issues with table corruption
• Poor replica MVCC support
• Difficulty upgrading to newer releases

Here, I am sharing the official link on UBER database migration. I completely read this article and agree with it on a few of the topics.
You guys must read carefully because we should understand the pros & cons of any RDBMS.

Before few days back, One of the SQL Server Developer asked me this question.
How to generate full database schema script or data script in PostgreSQL?

In PostgreSQL, We can also generate Database full script using Backup Option of PGAdmin tool.
When we require to create a fresh database without data, mostly we require to generate Database Schema Script.
We have one PLAIN text database backup type in PostgreSQL, which creates .sql file including Schema + Data.

Below are screenshots to generate Database Script using PGAdmin Tool:

Step 1:
Right click on the database and select backup option.
In backup dialog box, select PLAIN backup type and give a file name.

Step 2:
Default PLAIN text backup included both Database Schema + Data script.
In case of any changes, go to dump option tab and select data or schema only.

Step 3:
If you want to filter your objects, go to object tab and check or unchecked objects from the list.