Re: Restoring from SQL dump - Mailing list pgsql-novice

From Erin Jonaitis
Subject Re: Restoring from SQL dump
Date
Msg-id 00c901cecc0d$d42579b0$7c706d10$@wisc.edu
Whole thread Raw
In response to Re: Restoring from SQL dump  (Ken Benson <ken@infowerks.com>)
List pgsql-novice

Hi Ken,

 

Thanks for the idea. Tried that too, FWIW (using / instead of \), and it also failed silently, no errors. Pretty unfriendly behavior. I’m used to command lines yelling at me when I do something dumb, but this one just doesn’t.

 

Erin

 

From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Ken Benson
Sent: Friday, October 18, 2013 9:20 AM
To: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] Restoring from SQL dump

 

Try:
pg_restore M:\LongitudinalDB\backups\2013.10.02\uw.sql


On 10/18/2013 6:57 AM, Erin Jonaitis wrote:

Hello!

I am trying to restore data from an SQL dump. I am using Windows 7, PostgreSQL version 9.3, pgAdmin III 1.18.0.

 

Here is what I did.

 

1)      I used the pgAdmin III interface to create a new database.

2)      I selected this db in the console and selected Plugins > PSQL console.

3)      Now I have a psql window open with the following prompt:
dbname=#

4)      I tried typing the following:
psql –f M:\LongitudinalDB\backups\2013.10.02\uw.sql
and got the following error:
Invalid command \LongitudinalDB. Try \? For help.

5)      OK, so maybe the backslashes are the problem. I then tried
psql –f M:/LongitudinalDB/backups/2013.10.02/uw.sql
and got no error.

6)      However, none of the data or tables appeared in the db – it looks just as it did as a fresh db.

7)      I tried a few other things in the psql window, deliberately typing nonsense. No error messages then, either, just a fresh prompt.

 

Advice would be much appreciated.

 

Thanks,
Erin

 

pgsql-novice by date:

Previous
From: Erin Jonaitis
Date:
Subject: Re: Restoring from SQL dump
Next
From: Athanasios Kostopoulos
Date:
Subject: Re: Restoring from SQL dump