Re: Restoring from SQL dump

On Fri, Oct 18, 2013 at 10:58 AM, Erin Jonaitis <jonaitis@wisc.edu> wrote:
> I tried to follow Anathasios’ advice about setting the path variable, but on
> Windows7 this seems a bit opaque; I did add my PostgreSQL \bin directory to
> the Path variable through Control Panel (and I’ve checked my spelling three
> times), but I still have to be in that directory to run the program,
> strangely. So Ken’s example here, of how to give a full pathname for a
> command that isn’t in one of the %path% directories, is super useful.
>

Forgive me for asking the obvious question, but did you close and
re-open your command prompt?  Changes in the Path aren't detected
until you do that.   To check, do "echo %PATH%" (without the double
quotes), and it should print what you have for Path in the current
command prompt.

> To import it. (I say “it worked” optimistically because it is actually doing
> something, but there’ve been some periods where that “something” is
> “hanging” so we’re not out of the woods yet.)
>

Depending upon the speed of your computer and the size and schema of
your database, the load process can take a long time.  On slower disks
with a database that was just a few hundred MB when uncompressed, the
load process would sit at certain steps for over an hour for me.   If
you got that far, you're probably fine and all you have to do is wait.

-Mike