On 23 December 2015 at 11:19, Killian Driscoll <killiandrisc...@gmail.com> wrote:
> On 23 December 2015 at 11:07, John R Pierce <pie...@hogranch.com> wrote: > >> On 12/23/2015 1:40 AM, Killian Driscoll wrote: >> >> Try it with plain pg_dump. >>> >>> pg_dump -h localhost -p 5432 -Fc <dbname> > dump.sql >>> >>> pg_restore -h localhost -p 5532 dump.sql >>> >> >> I tried this, but nothing appears to happen when entering the commands. >> Attached is a screenshot of the shell window - what am I doing wrong? >> >> >> >> those are system shell commands, not psql sql commands. catch-22, in >> the windows environment, postgresql's command tools probably aren't in the >> path, so to execute the above commands try this... >> >> start -> run -> *CMD* <enter> >> >> (or, click on an 'Command Prompt' shortcut). >> >> C:\Users\YourName> *path "c:\Program >> Files\PostgreSQL\9.4\bin";%path%* >> C:\Users\YourName>* pg_dump -Fc -p 5432 **<dbname>** | pg_restore -p >> 5532* >> > Thanks. When I do this I get an error: could not find a "pg_dump" to > execute - I've used the path *"C:\Program > Files\PostgreSQL\9.3\bin";%path% *which appears to be correct > Sorry, forgot to add: once I get the warning that the Pg_dump can't be found there is then a password prompt; I tried the db password and the pc password but both fail: Password: pg_dump: [archiver (db)] connection to database "irll_project" failed: FATAL: p assword authentication failed for user "killian" pg_restore: [archiver] input file is too short (read 0, expected 5) > >> >> if your postgres is installed somewhere else, replace "c:\Program >> Files\PostgreSQL\9.4\bin" in the PATH command with its actual location >> \bin .... >> >> >> >> >> >> -- >> john r pierce, recycling bits in santa cruz >> >> >
