Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.55 minutes in January 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

How to use psql to restore a text dump?

by | Feb 10, 2021

Wondering how to use psql to restore a text dump?We can help you.

Using psql is one of the simplest ways to restore a text dump. Text dumping is a suitable importing method for small databases.

At Bobcares, we often get requests to restore text dumps, as a part of our Server Management Services.

Today, let’s discuss how to restore a text dump using psql (PostgreSQL) and see how our Support Engineers do this for our customers.

Steps for using psql to restore a text dump.

The dump method generates a SQL file of a database. Restoring this file recreates the database in the previous state.

Before going to the steps of restoring let’s see how to take a text dump file of a database.

Here we will use  pg_dump  to export a PostgreSQL database.

First, access the database directly or remotely to dump it. Now, dump the database using the following command.

pg_dump -U db_user -W -F p db_name > /path_of_the_dump/dump_file.sql

Here, the db_user is the database user and db_name is the database name. The other options are,

  • -U denotes a user.
  • -W prompt for a password before connecting to the server.
  • F denotes file format.

To dump the database in a text file format, use the option p.

Restoring a text dump:

Restoring a text dump file is only possible using psql. This is an interactive interface for managing the PostgreSQL database.

So,  for restoring the text dump we can take the psql console and run the following command.

psql -U db_user db_name < dump_file.sql

This restores the dump file successfully.

Common errors while using psql to restore a text dump

Sometimes the psql text dump restoring can end up in errors. Now, let’s see a few possible errors that occur during a text file restoration. We will also see how our Support Team fix these errors for our customers.

1. Invalid command while restoring sql

Sometimes, the psql dump restores ends up in the following error message.

psql:psit.sql:27485: invalid command \N

Here the \N denotes a null value. The error message itself is not much informative. In such situations, we will try to debug the error.

psql has an inbuilt mode ‘stop on the first error‘. So, we will switch psql to ‘stop on the first error mode’. This displays the initial trigger for the error. To switch the mode, we will use the following command:

psql -v ON_ERROR_STOP=1

This command gives the actual reason for the error which will help us to fix it.

2. Improper restoring of the dump file

At times we will encounter the following error message.

pg_restore: [archiver] input file appears to be a text format dump. Please use psql.

This error message is seen when the user tries to restore a text-based dump file using the pg_restore tool.

Usually, the pg_dump tool creates a dump file in text format. A single step restoration of a text file is only possible by using psql.

In order to use pg_restore, we must convert the text file to tar format and then execute the restore command.

So, to fix the error, we will restore the dump file in the appropriate format.

[Still, having trouble in restoring a text dump using psql? – We will help you.]


In short, psql restores a text dump in the same file format. Other restoration methods use different file formats and hence need file conversion. Today, we saw the text dump restoration and discussed how our Support Engineers fix the related errors.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

server management

Spend time on your business, not on your servers.


Or click here to learn more.