How to restore a PostgreSQL database from dump file in dbeaver?

Mary Smith

31 Aug 2023, 23:32 UTC

66.2K views1

In our company we have a dump of PostgreSQL database - file db.sql. It weighs 8 Gigabyte. How to restore this database in DBeaver? And we don't have another databases in DBeaver 7.0.5.

I have digged all Internet and haven't found anything how to do this without another database/

4,170 following

1 answer

Accepted answer · original discussion

jjanes

03 Sept 2023, 23:32 UTC

Permalink

When you right click on the database you want to restore into, under "Tools" you will find "execute script". This is how you restore a plain-format dump file, which is what db.sql probably is.

This will require you to have psql, but dbeaver will offer to download and install its own copy of it for you.

Your perspective belongs here.

0 question comments

Use comments to ask for clarification. Post a solution as an answer.

No question comments on this page.

Keep exploring this topic

Why does DBeaver fail to validate a PostgreSQL server's SSL certificate when the hostname resolves via DNS, and how can I configure a custom truststore to fix it?

Troubleshooting DBeaver SSL certificate validation failures linked to DNS hostname resolution when connecting to PostgreSQL over TLS.

Where are the postgres logs?

I'm using DBeaver to connect the postgres db and want to access the logs via DBeaver. I run the command below to find log destination and got stderr as the location. show log_destination ; How can I reach that file on DB app? FYI, I want all logs, not the logs that are from DBeaver.

DBeaver / PostgreSQL: "Error: database already exists", but I can't find it

I want to create database called "President" by rightclicking on PostgreSQL and selecting Create Database . However, I get the error in the screenprint below. I can create databases with other names like SomeOtherDatabase and SomeOtherDatabase2 (see screenprints). Any ideas how I can find and delete the database "President" that seems to

wal_level change in PostgreSQL 14 creates standby compatibility uncertainty after pg_upgrade

Unclear if a standby server must be restarted, reinitialized, or just reloaded after the primary’s wal_level changes from replica to logical in PostgreSQL 14.