Thread: Transfer db from one port to another
ERROR: syntax error at or near "\"
LINE 26: \connect irll_project
ALTER DATABASE irll_project OWNER TO postgres;
\connect irll_project
I have tried to use the Windows psql shell command to import using
\i 'C:/all.sql'
Hello
Why don’t you simply change the port in postgresql.conf and restart the server?
Bye
Charles
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Killian Driscoll
Sent: Mittwoch, 23. Dezember 2015 09:58
To: pgsql-general <pgsql-general@postgresql.org>
Subject: [GENERAL] Transfer db from one port to another
I am using Windows 8 64 bit, with postgreSQL 9.3 on port 5432 and postgreSQL 9.4 on port 5532 with the latter set up to use with Bitnami stack to test php files I am generating from my db.
I want to transfer my db with three schemas from port 5432 to port 5532 to use within the bitnami stack. I have used pgAdmin to create a backup.sql and when using pgAdmin to restore the .sql to port 5532 I get the following error
ERROR: syntax error at or near "\"
LINE 26: \connect irll_project
with the lines in the .sql file created being
ALTER DATABASE irll_project OWNER TO postgres;
\connect irll_project
I have tried to use the Windows psql shell command to import using
\i 'C:/all.sql'
on pressing enter I see multiple occurrences saying invalid command, and then it ends with
error: out of memory detail: failed on request of size 268435456
What is the correct command line?
Killian DriscoIl
Hello
Why don’t you simply change the port in postgresql.conf and restart the server?
Bye
Charles
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Killian Driscoll
Sent: Mittwoch, 23. Dezember 2015 09:58
To: pgsql-general <pgsql-general@postgresql.org>
Subject: [GENERAL] Transfer db from one port to another
I am using Windows 8 64 bit, with postgreSQL 9.3 on port 5432 and postgreSQL 9.4 on port 5532 with the latter set up to use with Bitnami stack to test php files I am generating from my db.
I want to transfer my db with three schemas from port 5432 to port 5532 to use within the bitnami stack. I have used pgAdmin to create a backup.sql and when using pgAdmin to restore the .sql to port 5532 I get the following error
ERROR: syntax error at or near "\"
LINE 26: \connect irll_projectwith the lines in the .sql file created being
ALTER DATABASE irll_project OWNER TO postgres;
\connect irll_project
I have tried to use the Windows psql shell command to import using
\i 'C:/all.sql'on pressing enter I see multiple occurrences saying invalid command, and then it ends with
error: out of memory detail: failed on request of size 268435456
What is the correct command line?
Killian DriscoIl
Killian Driscoll <killiandriscoll@gmail.com> wrote: > I am using Windows 8 64 bit, with postgreSQL 9.3 on port 5432 and postgreSQL > 9.4 on port 5532 with the latter set up to use with Bitnami stack to test php > files I am generating from my db. > > I want to transfer my db with three schemas from port 5432 to port 5532 to use > within the bitnami stack. I have used pgAdmin to create a backup.sql and when > using pgAdmin to restore the .sql to port 5532 I get the following error Try it with plain pg_dump. pg_dump -h localhost -p 5432 -Fc <dbname> > dump.sql pg_restore -h localhost -p 5532 dump.sql (untestet, please read *before* the documentation) I think, this should work. No idea what's wrong with pgAdmin, not using that. Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
Charles Clavadetscher <clavadetscher@swisspug.org> wrote: > Hello > > > > Why don’t you simply change the port in postgresql.conf and restart the server? i think, he wants the data from the one database within the other, because of that he can't change the port. Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
Killian Driscoll <killiandriscoll@gmail.com> wrote:
> I am using Windows 8 64 bit, with postgreSQL 9.3 on port 5432 and postgreSQL
> 9.4 on port 5532 with the latter set up to use with Bitnami stack to test php
> files I am generating from my db.
>
> I want to transfer my db with three schemas from port 5432 to port 5532 to use
> within the bitnami stack. I have used pgAdmin to create a backup.sql and when
> using pgAdmin to restore the .sql to port 5532 I get the following error
Try it with plain pg_dump.
pg_dump -h localhost -p 5432 -Fc <dbname> > dump.sql
pg_restore -h localhost -p 5532 dump.sql
(untestet, please read *before* the documentation)
I think, this should work. No idea what's wrong with pgAdmin, not using
that.
Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Attachment
Hello Killian >> I want to transfer my db with three schemas from port 5432 to port 5532 to use >> within the bitnami stack. I have used pgAdmin to create a backup.sql and when >> using pgAdmin to restore the .sql to port 5532 I get the following error > >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 - whatam I doing wrong? This should be done from an OS shell, not from psql. Bye Charles (untestet, please read *before* the documentation) I think, this should work. No idea what's wrong with pgAdmin, not using that. Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889° -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Hello Killian
>> I want to transfer my db with three schemas from port 5432 to port 5532 to use
>> within the bitnami stack. I have used pgAdmin to create a backup.sql and when
>> using pgAdmin to restore the .sql to port 5532 I get the following error
>
>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?
This should be done from an OS shell, not from psql.
Bye
Charles
(untestet, please read *before* the documentation)
I think, this should work. No idea what's wrong with pgAdmin, not using
that.
Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
From: Killian Driscoll [mailto:killiandriscoll@gmail.com]
Sent: Mittwoch, 23. Dezember 2015 11:02
To: Charles Clavadetscher <clavadetscher@swisspug.org>
Cc: Andreas Kretschmer <akretschmer@spamfence.net>; pgsql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Transfer db from one port to another
On 23 December 2015 at 10:58, Charles Clavadetscher <clavadetscher@swisspug.org> wrote:
Hello Killian
>> I want to transfer my db with three schemas from port 5432 to port 5532 to use
>> within the bitnami stack. I have used pgAdmin to create a backup.sql and when
>> using pgAdmin to restore the .sql to port 5532 I get the following error
>
>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?
This should be done from an OS shell, not from psql.
Do you mean Windows command prompt?
Yes
Bye
Charles
(untestet, please read *before* the documentation)
I think, this should work. No idea what's wrong with pgAdmin, not using
that.
Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Try it with plain pg_dump.
pg_dump -h localhost -p 5432 -Fc <dbname> > dump.sql
pg_restore -h localhost -p 5532 dump.sqlI 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
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
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.sqlI 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
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
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Killian Driscoll
Sent: Mittwoch, 23. Dezember 2015 11:19
To: John R Pierce <pierce@hogranch.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Transfer db from one port to another
On 23 December 2015 at 11:07, John R Pierce <pierce@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
You may try calling the app without setting the path first or check the location browsing the file system:
C:\Program Files\PostgreSQL\9.3\bin\ pg_dump -Fc -p 5432 <dbname>
Don’t forget to replace <dbname> with the database that you want to dump.
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
On 23 December 2015 at 11:07, John R Pierce <pierce@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.sqlI 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 5532Thanks. 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
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
(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 5532Thanks. 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
to test this, try (at that same command prompt)
dir "C:\Program Files\PostgreSQL\9.3\bin"that should list the postgres utilities and stuff, including psql.exe, pg_dump.exe, etc.
like, on a system here (which uses a non-default path), its ...
C:\Users\xxxx>dir "d:\PostgreSQL\9.3\bin"
Volume in drive D is Drive_Dee
Volume Serial Number is ****
Directory of d:\PostgreSQL\9.3\bin
09/30/2014 12:28 AM <DIR> .
09/30/2014 12:28 AM <DIR> ..
07/21/2014 11:51 PM 69,120 clusterdb.exe
...
07/21/2014 11:51 PM 384,000 pg_dump.exe
...
07/21/2014 11:51 PM 180,736 pg_restore.exe
...
07/21/2014 11:51 PM 408,576 psql.exe
...
02/05/2014 01:33 AM 77,824 zlib1.dll
70 File(s) 56,177,637 bytes
3 Dir(s) 1,687,179,091,968 bytes free
C:\Users\xxxx>
(note I trimmed about 65 files)
-- john r pierce, recycling bits in santa cruz
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Killian Driscoll
Sent: Mittwoch, 23. Dezember 2015 11:26
To: John R Pierce <pierce@hogranch.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Transfer db from one port to another
On 23 December 2015 at 11:19, Killian Driscoll <killiandriscoll@gmail.com> wrote:
On 23 December 2015 at 11:07, John R Pierce <pierce@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 5532Thanks. 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"
Do you have a user killian in the database? If not you can either create it or use pg_dump with the –U switch to set it to the existing user (and with privileges on the database of course).
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
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"
note that databases don't have passwords, database USERS have passwords. 'killian' probably doesn't have a database user, and since you didn't specify a user, it defaulted to your system username (expecting that user to have been created in postgres, and wanting that probably non-existant postgres users passsword)
so, ok, try the command with -U postgres, as
pg_dump -Fc -p 5432 -U postgres irll_project | pg_restore -U postgres -p 5532if/when it prompts for a password, thats the password of the 'postgres' database user, as configured in the postgres servers.
note it will prompt for the password a couple times, once for postgres on port 5432, and again for postgres on port 5532, at least if both database services are configured to require passwords for local connections.
-- john r pierce, recycling bits in santa cruz
On 12/23/2015 2:25 AM, Killian Driscoll wrote: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"
note that databases don't have passwords, database USERS have passwords. 'killian' probably doesn't have a database user, and since you didn't specify a user, it defaulted to your system username (expecting that user to have been created in postgres, and wanting that probably non-existant postgres users passsword)
so, ok, try the command with -U postgres, aspg_dump -Fc -p 5432 -U postgres irll_project | pg_restore -U postgres -p 5532
09/06/2014 08:35 381,952 pg_dump.exe
09/06/2014 08:35 180,224 pg_restore.exe
C:\Users\killian>path "C:\Program Files\PostgreSQL\9.3\bin";%path%
C:\Users\killian>pg_dump -Fc -p 5432 -U postgres irll_project | pg_restore -U po
stgres -p 5532
ccoulould not findd a n "pg_restore" to executeot find a "pg_dump" to execute
pg_restore: [archiver] did not find magic string in file header
pg_dump: [custom archiver] could not write to output file: Invalid argument
if/when it prompts for a password, thats the password of the 'postgres' database user, as configured in the postgres servers.
note it will prompt for the password a couple times, once for postgres on port 5432, and again for postgres on port 5532, at least if both database services are configured to require passwords for local connections.-- john r pierce, recycling bits in santa cruz
On 12/23/2015 03:43 AM, Killian Driscoll wrote: > On 23 December 2015 at 11:36, John R Pierce <pierce@hogranch.com > <mailto:pierce@hogranch.com>> wrote: > > On 12/23/2015 2:25 AM, Killian Driscoll wrote: >> 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" > > note that databases don't have passwords, database USERS have > passwords. 'killian' probably doesn't have a database user, and > since you didn't specify a user, it defaulted to your system > username (expecting that user to have been created in postgres, and > wanting that probably non-existant postgres users passsword) > > so, ok, try the command with -U postgres, as * > * > > *pg_dump -Fc -p 5432 **-U postgres **irll_project | pg_restore > -U postgres -p 5532* > > OK - I did the dir and it shows that the dump and restore.exe are there, > but running the above gives the below errors > > 09/06/2014 08:35 381,952 pg_dump.exe > > 09/06/2014 08:35 180,224 pg_restore.exe > > C:\Users\killian>path "C:\Program Files\PostgreSQL\9.3\bin";%path% > > C:\Users\killian>pg_dump -Fc -p 5432 -U postgres irll_project | > pg_restore -U po > stgres -p 5532 > ccoulould not findd a n "pg_restore" to executeot find a "pg_dump" to > execute > > pg_restore: [archiver] did not find magic string in file header > pg_dump: [custom archiver] could not write to output file: Invalid argument Try breaking the above down into two steps: pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project pg_restore -U postgres -p 5532 irll_project.out > > > if/when it prompts for a password, thats the password of the > 'postgres' database user, as configured in the postgres servers. > > note it will prompt for the password a couple times, once for > postgres on port 5432, and again for postgres on port 5532, at least > if both database services are configured to require passwords for > local connections. > > > -- > john r pierce, recycling bits in santa cruz > > -- Adrian Klaver adrian.klaver@aklaver.com
On 12/23/2015 03:43 AM, Killian Driscoll wrote:On 23 December 2015 at 11:36, John R Pierce <pierce@hogranch.com
<mailto:pierce@hogranch.com>> wrote:
On 12/23/2015 2:25 AM, Killian Driscoll wrote: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"
note that databases don't have passwords, database USERS have
passwords. 'killian' probably doesn't have a database user, and
since you didn't specify a user, it defaulted to your system
username (expecting that user to have been created in postgres, and
wanting that probably non-existant postgres users passsword)
so, ok, try the command with -U postgres, as *
*
*pg_dump -Fc -p 5432 **-U postgres **irll_project | pg_restore
-U postgres -p 5532*
OK - I did the dir and it shows that the dump and restore.exe are there,
but running the above gives the below errors
09/06/2014 08:35 381,952 pg_dump.exe
09/06/2014 08:35 180,224 pg_restore.exe
C:\Users\killian>path "C:\Program Files\PostgreSQL\9.3\bin";%path%
C:\Users\killian>pg_dump -Fc -p 5432 -U postgres irll_project |
pg_restore -U po
stgres -p 5532
ccoulould not findd a n "pg_restore" to executeot find a "pg_dump" to
execute
pg_restore: [archiver] did not find magic string in file header
pg_dump: [custom archiver] could not write to output file: Invalid argument
Try breaking the above down into two steps:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project
pg_restore -U postgres -p 5532 irll_project.out--
if/when it prompts for a password, thats the password of the
'postgres' database user, as configured in the postgres servers.
note it will prompt for the password a couple times, once for
postgres on port 5432, and again for postgres on port 5532, at least
if both database services are configured to require passwords for
local connections.
--
john r pierce, recycling bits in santa cruz
Adrian Klaver
adrian.klaver@aklaver.com
> On 23 Dec 2015, at 12:43, Killian Driscoll <killiandriscoll@gmail.com> wrote: > > OK - I did the dir and it shows that the dump and restore.exe are there, but running the above gives the below errors > > 09/06/2014 08:35 381,952 pg_dump.exe > > 09/06/2014 08:35 180,224 pg_restore.exe > > C:\Users\killian>path "C:\Program Files\PostgreSQL\9.3\bin";%path% > > C:\Users\killian>pg_dump -Fc -p 5432 -U postgres irll_project | pg_restore -U po > stgres -p 5532 > ccoulould not findd a n "pg_restore" to executeot find a "pg_dump" to execute Aren't you trying to move a database to PG 9.4? Then you need to use the pg_dump and pg_restore utilities of the 9.4 installation,not those of the 9.3 one. Those utilities are guaranteed to be backwards compatible, but they're not necessarilyforwards compatible. Alban Hertroys -- If you can't see the forest for the trees, cut the trees and you'll find there is no forest.
We had that already upthread.
Did you set the path to the bin dir of PostgreSQL as of previous posts?
Regards
Charles
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Killian Driscoll
Sent: Mittwoch, 23. Dezember 2015 15:14
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: John R Pierce <pierce@hogranch.com>; pgsql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Transfer db from one port to another
On 23 December 2015 at 14:56, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 12/23/2015 03:43 AM, Killian Driscoll wrote:
On 23 December 2015 at 11:36, John R Pierce <pierce@hogranch.com
<mailto:pierce@hogranch.com>> wrote:
On 12/23/2015 2:25 AM, Killian Driscoll wrote: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"
note that databases don't have passwords, database USERS have
passwords. 'killian' probably doesn't have a database user, and
since you didn't specify a user, it defaulted to your system
username (expecting that user to have been created in postgres, and
wanting that probably non-existant postgres users passsword)
so, ok, try the command with -U postgres, as *
*
*pg_dump -Fc -p 5432 **-U postgres **irll_project | pg_restore
-U postgres -p 5532*
OK - I did the dir and it shows that the dump and restore.exe are there,
but running the above gives the below errors
09/06/2014 08:35 381,952 pg_dump.exe
09/06/2014 08:35 180,224 pg_restore.exe
C:\Users\killian>path "C:\Program Files\PostgreSQL\9.3\bin";%path%
C:\Users\killian>pg_dump -Fc -p 5432 -U postgres irll_project |
pg_restore -U po
stgres -p 5532
ccoulould not findd a n "pg_restore" to executeot find a "pg_dump" to
execute
pg_restore: [archiver] did not find magic string in file header
pg_dump: [custom archiver] could not write to output file: Invalid argument
Try breaking the above down into two steps:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project
Doing this step I get response
could not find a "pg_dump" to execute
pg_restore -U postgres -p 5532 irll_project.out
if/when it prompts for a password, thats the password of the
'postgres' database user, as configured in the postgres servers.
note it will prompt for the password a couple times, once for
postgres on port 5432, and again for postgres on port 5532, at least
if both database services are configured to require passwords for
local connections.
--
john r pierce, recycling bits in santa cruz
--
Adrian Klaver
adrian.klaver@aklaver.com
On 12/23/2015 06:13 AM, Killian Driscoll wrote: > On 23 December 2015 at 14:56, Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > On 12/23/2015 03:43 AM, Killian Driscoll wrote: > > On 23 December 2015 at 11:36, John R Pierce <pierce@hogranch.com > <mailto:pierce@hogranch.com> > <mailto:pierce@hogranch.com <mailto:pierce@hogranch.com>>> wrote: > > On 12/23/2015 2:25 AM, Killian Driscoll wrote: > > 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" > > > note that databases don't have passwords, database USERS have > passwords. 'killian' probably doesn't have a database > user, and > since you didn't specify a user, it defaulted to your system > username (expecting that user to have been created in > postgres, and > wanting that probably non-existant postgres users passsword) > > so, ok, try the command with -U postgres, as * > * > > *pg_dump -Fc -p 5432 **-U postgres **irll_project | > pg_restore > -U postgres -p 5532* > > OK - I did the dir and it shows that the dump and restore.exe > are there, > but running the above gives the below errors > > 09/06/2014 08:35 381,952 pg_dump.exe > > 09/06/2014 08:35 180,224 pg_restore.exe > > C:\Users\killian>path "C:\Program Files\PostgreSQL\9.3\bin";%path% > > C:\Users\killian>pg_dump -Fc -p 5432 -U postgres irll_project | > pg_restore -U po > stgres -p 5532 > ccoulould not findd a n "pg_restore" to executeot find a > "pg_dump" to > execute > > pg_restore: [archiver] did not find magic string in file header > pg_dump: [custom archiver] could not write to output file: > Invalid argument > > > > Try breaking the above down into two steps: > > pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project > > > Doing this step I get response > could not find a "pg_dump" to execute So cd into: C:\Program Files\PostgreSQL\9.3\bin and try: pg_dump --help that will at least establish that the command is being found. > > > pg_restore -U postgres -p 5532 irll_project.out > > > > > if/when it prompts for a password, thats the password of the > 'postgres' database user, as configured in the postgres > servers. > > note it will prompt for the password a couple times, once for > postgres on port 5432, and again for postgres on port 5532, > at least > if both database services are configured to require > passwords for > local connections. > > > -- > john r pierce, recycling bits in santa cruz > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > -- Adrian Klaver adrian.klaver@aklaver.com
On 12/23/2015 06:13 AM, Killian Driscoll wrote:On 23 December 2015 at 14:56, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
On 12/23/2015 03:43 AM, Killian Driscoll wrote:
On 23 December 2015 at 11:36, John R Pierce <pierce@hogranch.com
<mailto:pierce@hogranch.com><mailto:pierce@hogranch.com <mailto:pierce@hogranch.com>>> wrote:
On 12/23/2015 2:25 AM, Killian Driscoll wrote:
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"
note that databases don't have passwords, database USERS have
passwords. 'killian' probably doesn't have a database
user, and
since you didn't specify a user, it defaulted to your system
username (expecting that user to have been created in
postgres, and
wanting that probably non-existant postgres users passsword)
so, ok, try the command with -U postgres, as *
*
*pg_dump -Fc -p 5432 **-U postgres **irll_project |
pg_restore
-U postgres -p 5532*
OK - I did the dir and it shows that the dump and restore.exe
are there,
but running the above gives the below errors
09/06/2014 08:35 381,952 pg_dump.exe
09/06/2014 08:35 180,224 pg_restore.exe
C:\Users\killian>path "C:\Program Files\PostgreSQL\9.3\bin";%path%
C:\Users\killian>pg_dump -Fc -p 5432 -U postgres irll_project |
pg_restore -U po
stgres -p 5532
ccoulould not findd a n "pg_restore" to executeot find a
"pg_dump" to
execute
pg_restore: [archiver] did not find magic string in file header
pg_dump: [custom archiver] could not write to output file:
Invalid argument
Try breaking the above down into two steps:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project
Doing this step I get response
could not find a "pg_dump" to execute
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the command is being found.
pg_restore -U postgres -p 5532 irll_project.out
if/when it prompts for a password, thats the password of the
'postgres' database user, as configured in the postgres
servers.
note it will prompt for the password a couple times, once for
postgres on port 5432, and again for postgres on port 5532,
at least
if both database services are configured to require
passwords for
local connections.
--
john r pierce, recycling bits in santa cruz
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
On 12/23/2015 06:35 AM, Killian Driscoll wrote: > On 23 December 2015 at 15:30, Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > On 12/23/2015 06:13 AM, Killian Driscoll wrote: > > On 23 December 2015 at 14:56, Adrian Klaver > <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>>> wrote: > > On 12/23/2015 03:43 AM, Killian Driscoll wrote: > > On 23 December 2015 at 11:36, John R Pierce > <pierce@hogranch.com <mailto:pierce@hogranch.com> > <mailto:pierce@hogranch.com <mailto:pierce@hogranch.com>> > <mailto:pierce@hogranch.com > <mailto:pierce@hogranch.com> <mailto:pierce@hogranch.com > <mailto:pierce@hogranch.com>>>> wrote: > > On 12/23/2015 2:25 AM, Killian Driscoll wrote: > > 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" > > > note that databases don't have passwords, database > USERS have > passwords. 'killian' probably doesn't have a database > user, and > since you didn't specify a user, it defaulted to > your system > username (expecting that user to have been created in > postgres, and > wanting that probably non-existant postgres users > passsword) > > so, ok, try the command with -U postgres, as * > * > > *pg_dump -Fc -p 5432 **-U postgres > **irll_project | > pg_restore > -U postgres -p 5532* > > OK - I did the dir and it shows that the dump and > restore.exe > are there, > but running the above gives the below errors > > 09/06/2014 08:35 381,952 pg_dump.exe > > 09/06/2014 08:35 180,224 pg_restore.exe > > C:\Users\killian>path "C:\Program > Files\PostgreSQL\9.3\bin";%path% > > C:\Users\killian>pg_dump -Fc -p 5432 -U postgres > irll_project | > pg_restore -U po > stgres -p 5532 > ccoulould not findd a n "pg_restore" to executeot find a > "pg_dump" to > execute > > pg_restore: [archiver] did not find magic string in > file header > pg_dump: [custom archiver] could not write to output file: > Invalid argument > > > > Try breaking the above down into two steps: > > pg_dump -Fc -p 5432 -U postgres -f irll_project.out > irll_project > > > Doing this step I get response > could not find a "pg_dump" to execute > > > So cd into: > > C:\Program Files\PostgreSQL\9.3\bin > > and try: > > pg_dump --help > > that will at least establish that the command is being found. > > > OK - --help on the 9.3 lists help options In your original post you said you have a 9.3 instance and a 9.4 instance. From your post I would say the 9.3 instance was installed by the one click installer from EDB and the 9.4 from Bitami, is that correct? So do you know where the 9.4 binaries are installed? > > > > > pg_restore -U postgres -p 5532 irll_project.out > > > > > if/when it prompts for a password, thats the > password of the > 'postgres' database user, as configured in the > postgres > servers. > > note it will prompt for the password a couple > times, once for > postgres on port 5432, and again for postgres on > port 5532, > at least > if both database services are configured to require > passwords for > local connections. > > > -- > john r pierce, recycling bits in santa cruz > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > -- Adrian Klaver adrian.klaver@aklaver.com
On 12/23/2015 06:35 AM, Killian Driscoll wrote:On 23 December 2015 at 15:30, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
On 12/23/2015 06:13 AM, Killian Driscoll wrote:
On 23 December 2015 at 14:56, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>> wrote:
On 12/23/2015 03:43 AM, Killian Driscoll wrote:
On 23 December 2015 at 11:36, John R Pierce
<pierce@hogranch.com <mailto:pierce@hogranch.com>
<mailto:pierce@hogranch.com <mailto:pierce@hogranch.com>>
<mailto:pierce@hogranch.com
<mailto:pierce@hogranch.com> <mailto:pierce@hogranch.com
<mailto:pierce@hogranch.com>>>> wrote:
On 12/23/2015 2:25 AM, Killian Driscoll wrote:
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"
note that databases don't have passwords, database
USERS have
passwords. 'killian' probably doesn't have a database
user, and
since you didn't specify a user, it defaulted to
your system
username (expecting that user to have been created in
postgres, and
wanting that probably non-existant postgres users
passsword)
so, ok, try the command with -U postgres, as *
*
*pg_dump -Fc -p 5432 **-U postgres
**irll_project |
pg_restore
-U postgres -p 5532*
OK - I did the dir and it shows that the dump and
restore.exe
are there,
but running the above gives the below errors
09/06/2014 08:35 381,952 pg_dump.exe
09/06/2014 08:35 180,224 pg_restore.exe
C:\Users\killian>path "C:\Program
Files\PostgreSQL\9.3\bin";%path%
C:\Users\killian>pg_dump -Fc -p 5432 -U postgres
irll_project |
pg_restore -U po
stgres -p 5532
ccoulould not findd a n "pg_restore" to executeot find a
"pg_dump" to
execute
pg_restore: [archiver] did not find magic string in
file header
pg_dump: [custom archiver] could not write to output file:
Invalid argument
Try breaking the above down into two steps:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out
irll_project
Doing this step I get response
could not find a "pg_dump" to execute
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the command is being found.
OK - --help on the 9.3 lists help options
In your original post you said you have a 9.3 instance and a 9.4 instance.
From your post I would say the 9.3 instance was installed by the one click installer from EDB and the 9.4 from Bitami, is that correct?
So do you know where the 9.4 binaries are installed?
pg_restore -U postgres -p 5532 irll_project.out
if/when it prompts for a password, thats the
password of the
'postgres' database user, as configured in the
postgres
servers.
note it will prompt for the password a couple
times, once for
postgres on port 5432, and again for postgres on
port 5532,
at least
if both database services are configured to require
passwords for
local connections.
--
john r pierce, recycling bits in santa cruz
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
On 12/23/2015 06:50 AM, Killian Driscoll wrote: > On 23 December 2015 at 15:47, Adrian Klaver <adrian.klaver@aklaver.com > > So cd into: > > C:\Program Files\PostgreSQL\9.3\bin > > and try: > > pg_dump --help > > that will at least establish that the command is being found. > > > OK - --help on the 9.3 lists help options > > > In your original post you said you have a 9.3 instance and a 9.4 > instance. > > >From your post I would say the 9.3 instance was installed by the > one click installer from EDB and the 9.4 from Bitami, is that correct? > > Correct. > > > So do you know where the 9.4 binaries are installed? > > If by binaries, you mean the program files they are installed > C:\Bitnami\wappstack-5.5.30-0\postgresql\bin Per previous posts you want, whenever possible, to us a newer version of pg_dump to move a database from an older version(9.3) to a newer one(9.4). Therefore you should do your dump and restore using the pg_dump.exe and pg_restore.exe from the Bitanami bin directory. I would cd to the above directory and do: pg_dump -V pg_restore -V to make sure the programs are found and are the 9.4 versions. Then do: pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project pg_restore -U postgres -p 5532 irll_project.out > > > -- Adrian Klaver adrian.klaver@aklaver.com
On 12/23/2015 06:50 AM, Killian Driscoll wrote:On 23 December 2015 at 15:47, Adrian Klaver <adrian.klaver@aklaver.com
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the command is being found.
OK - --help on the 9.3 lists help options
In your original post you said you have a 9.3 instance and a 9.4
instance.
>From your post I would say the 9.3 instance was installed by the
one click installer from EDB and the 9.4 from Bitami, is that correct?
Correct.
So do you know where the 9.4 binaries are installed?
If by binaries, you mean the program files they are installed
C:\Bitnami\wappstack-5.5.30-0\postgresql\bin
Per previous posts you want, whenever possible, to us a newer version of pg_dump to move a database from an older version(9.3) to a newer one(9.4). Therefore you should do your dump and restore using the pg_dump.exe and pg_restore.exe from the Bitanami bin directory. I would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_projectpg_restore -U postgres -p 5532 irll_project.out
--
Adrian Klaver
adrian.klaver@aklaver.com
On 12/23/2015 11:03 AM, Killian Driscoll wrote: > On 23 December 2015 at 16:02, Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > On 12/23/2015 06:50 AM, Killian Driscoll wrote: > > On 23 December 2015 at 15:47, Adrian Klaver > <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > > > So cd into: > > C:\Program Files\PostgreSQL\9.3\bin > > and try: > > pg_dump --help > > that will at least establish that the command is > being found. > > > OK - --help on the 9.3 lists help options > > > In your original post you said you have a 9.3 instance and > a 9.4 > instance. > > >From your post I would say the 9.3 instance was installed > by the > one click installer from EDB and the 9.4 from Bitami, is > that correct? > > Correct. > > > So do you know where the 9.4 binaries are installed? > > If by binaries, you mean the program files they are installed > C:\Bitnami\wappstack-5.5.30-0\postgresql\bin > > > Per previous posts you want, whenever possible, to us a newer > version of pg_dump to move a database from an older version(9.3) to > a newer one(9.4). Therefore you should do your dump and restore > using the pg_dump.exe and pg_restore.exe from the Bitanami bin > directory. I would cd to the above directory and do: > > pg_dump -V > pg_restore -V > > to make sure the programs are found and are the 9.4 versions. > > Then do: > > pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project > > pg_restore -U postgres -p 5532 irll_project.out > > > It appeared to work with this method, but it has now been running for > almost 4 hours with no result. The db is not that large (probably v. > small by most standards) and the .out file is ~200mb What is running, the dump or the restore? > > > > > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > -- Adrian Klaver adrian.klaver@aklaver.com
On 12/23/2015 11:03 AM, Killian Driscoll wrote:On 23 December 2015 at 16:02, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
On 12/23/2015 06:50 AM, Killian Driscoll wrote:
On 23 December 2015 at 15:47, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the command is
being found.
OK - --help on the 9.3 lists help options
In your original post you said you have a 9.3 instance and
a 9.4
instance.
>From your post I would say the 9.3 instance was installed
by the
one click installer from EDB and the 9.4 from Bitami, is
that correct?
Correct.
So do you know where the 9.4 binaries are installed?
If by binaries, you mean the program files they are installed
C:\Bitnami\wappstack-5.5.30-0\postgresql\bin
Per previous posts you want, whenever possible, to us a newer
version of pg_dump to move a database from an older version(9.3) to
a newer one(9.4). Therefore you should do your dump and restore
using the pg_dump.exe and pg_restore.exe from the Bitanami bin
directory. I would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project
pg_restore -U postgres -p 5532 irll_project.out
It appeared to work with this method, but it has now been running for
almost 4 hours with no result. The db is not that large (probably v.
small by most standards) and the .out file is ~200mb
What is running, the dump or the restore?
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
On 12/23/2015 11:09 AM, Killian Driscoll wrote: > On 23 December 2015 at 20:07, Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > On 12/23/2015 11:03 AM, Killian Driscoll wrote: > > On 23 December 2015 at 16:02, Adrian Klaver > <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>>> wrote: > > On 12/23/2015 06:50 AM, Killian Driscoll wrote: > > On 23 December 2015 at 15:47, Adrian Klaver > <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> > > > > > So cd into: > > C:\Program Files\PostgreSQL\9.3\bin > > and try: > > pg_dump --help > > that will at least establish that the > command is > being found. > > > OK - --help on the 9.3 lists help options > > > In your original post you said you have a 9.3 > instance and > a 9.4 > instance. > > >From your post I would say the 9.3 instance was > installed > by the > one click installer from EDB and the 9.4 from > Bitami, is > that correct? > > Correct. > > > So do you know where the 9.4 binaries are installed? > > If by binaries, you mean the program files they are > installed > C:\Bitnami\wappstack-5.5.30-0\postgresql\bin > > > Per previous posts you want, whenever possible, to us a newer > version of pg_dump to move a database from an older > version(9.3) to > a newer one(9.4). Therefore you should do your dump and restore > using the pg_dump.exe and pg_restore.exe from the Bitanami bin > directory. I would cd to the above directory and do: > > pg_dump -V > pg_restore -V > > to make sure the programs are found and are the 9.4 versions. > > Then do: > > pg_dump -Fc -p 5432 -U postgres -f irll_project.out > irll_project > > pg_restore -U postgres -p 5532 irll_project.out > > > It appeared to work with this method, but it has now been > running for > almost 4 hours with no result. The db is not that large (probably v. > small by most standards) and the .out file is ~200mb > > > What is running, the dump or the restore? > > The restore - I can see the dump .out file that was created at 16hr in > the postgresql/bin folder So how are you determining it is running and that it is not doing anything? What does the Postgres log for the 9.4 instance show? > > > > > > > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > -- Adrian Klaver adrian.klaver@aklaver.com
On 12/23/2015 11:09 AM, Killian Driscoll wrote:On 23 December 2015 at 20:07, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
On 12/23/2015 11:03 AM, Killian Driscoll wrote:
On 23 December 2015 at 16:02, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>> wrote:
On 12/23/2015 06:50 AM, Killian Driscoll wrote:
On 23 December 2015 at 15:47, Adrian Klaver
<adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the
command is
being found.
OK - --help on the 9.3 lists help options
In your original post you said you have a 9.3
instance and
a 9.4
instance.
>From your post I would say the 9.3 instance was
installed
by the
one click installer from EDB and the 9.4 from
Bitami, is
that correct?
Correct.
So do you know where the 9.4 binaries are installed?
If by binaries, you mean the program files they are
installed
C:\Bitnami\wappstack-5.5.30-0\postgresql\bin
Per previous posts you want, whenever possible, to us a newer
version of pg_dump to move a database from an older
version(9.3) to
a newer one(9.4). Therefore you should do your dump and restore
using the pg_dump.exe and pg_restore.exe from the Bitanami bin
directory. I would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out
irll_project
pg_restore -U postgres -p 5532 irll_project.out
It appeared to work with this method, but it has now been
running for
almost 4 hours with no result. The db is not that large (probably v.
small by most standards) and the .out file is ~200mb
What is running, the dump or the restore?
The restore - I can see the dump .out file that was created at 16hr in
the postgresql/bin folder
So how are you determining it is running and that it is not doing anything?
What does the Postgres log for the 9.4 instance show?
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
SELECT datname,
pid as pid,
client_addr,
usename as user,
query,
CASE WHEN waiting = TRUE
THEN 'BLOCKED'
ELSE 'no'
END as waiting,
query_start,
current_timestamp - query_start as duration
FROM pg_stat_activity
WHERE pg_backend_pid() <> pid
ORDER BY datname,
query_start;
On 12/23/2015 11:09 AM, Killian Driscoll wrote:On 23 December 2015 at 20:07, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
On 12/23/2015 11:03 AM, Killian Driscoll wrote:
On 23 December 2015 at 16:02, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>> wrote:
On 12/23/2015 06:50 AM, Killian Driscoll wrote:
On 23 December 2015 at 15:47, Adrian Klaver
<adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the
command is
being found.
OK - --help on the 9.3 lists help options
In your original post you said you have a 9.3
instance and
a 9.4
instance.
>From your post I would say the 9.3 instance was
installed
by the
one click installer from EDB and the 9.4 from
Bitami, is
that correct?
Correct.
So do you know where the 9.4 binaries are installed?
If by binaries, you mean the program files they are
installed
C:\Bitnami\wappstack-5.5.30-0\postgresql\bin
Per previous posts you want, whenever possible, to us a newer
version of pg_dump to move a database from an older
version(9.3) to
a newer one(9.4). Therefore you should do your dump and restore
using the pg_dump.exe and pg_restore.exe from the Bitanami bin
directory. I would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out
irll_project
pg_restore -U postgres -p 5532 irll_project.out
It appeared to work with this method, but it has now been
running for
almost 4 hours with no result. The db is not that large (probably v.
small by most standards) and the .out file is ~200mb
What is running, the dump or the restore?
The restore - I can see the dump .out file that was created at 16hr in
the postgresql/bin folder
So how are you determining it is running and that it is not doing anything?
What does the Postgres log for the 9.4 instance show?
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
![](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif)
It's possible the restore is still building indexes.What does it show when you run this query?
SELECT datname,
pid as pid,
client_addr,
usename as user,
query,
CASE WHEN waiting = TRUE
THEN 'BLOCKED'
ELSE 'no'
END as waiting,
query_start,
current_timestamp - query_start as duration
FROM pg_stat_activity
WHERE pg_backend_pid() <> pid
ORDER BY datname,
query_start;On Wed, Dec 23, 2015 at 2:14 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:09 AM, Killian Driscoll wrote:On 23 December 2015 at 20:07, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
On 12/23/2015 11:03 AM, Killian Driscoll wrote:
On 23 December 2015 at 16:02, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>> wrote:
On 12/23/2015 06:50 AM, Killian Driscoll wrote:
On 23 December 2015 at 15:47, Adrian Klaver
<adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the
command is
being found.
OK - --help on the 9.3 lists help options
In your original post you said you have a 9.3
instance and
a 9.4
instance.
>From your post I would say the 9.3 instance was
installed
by the
one click installer from EDB and the 9.4 from
Bitami, is
that correct?
Correct.
So do you know where the 9.4 binaries are installed?
If by binaries, you mean the program files they are
installed
C:\Bitnami\wappstack-5.5.30-0\postgresql\bin
Per previous posts you want, whenever possible, to us a newer
version of pg_dump to move a database from an older
version(9.3) to
a newer one(9.4). Therefore you should do your dump and restore
using the pg_dump.exe and pg_restore.exe from the Bitanami bin
directory. I would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out
irll_project
pg_restore -U postgres -p 5532 irll_project.out
It appeared to work with this method, but it has now been
running for
almost 4 hours with no result. The db is not that large (probably v.
small by most standards) and the .out file is ~200mb
What is running, the dump or the restore?
The restore - I can see the dump .out file that was created at 16hr in
the postgresql/bin folder
So how are you determining it is running and that it is not doing anything?
What does the Postgres log for the 9.4 instance show?
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
On 12/23/2015 11:17 AM, Killian Driscoll wrote: > On 23 December 2015 at 20:14, Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > > So how are you determining it is running and that it is not doing > anything? > > Since I ran the restore the windows shell has been 'active' with codes > lines running - I took that as being active.....! So what do they say? > > > What does the Postgres log for the 9.4 instance show? > > Where is the log - here Control Panel\System and Security\Administrative > Tools in event viewer or elsewhere? My guess in the Bitnami directory tree under logs/ or something similar. > > > > > > > > > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>>> > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > -- Adrian Klaver adrian.klaver@aklaver.com
Just run psql from the command shell in the Bitnami binary directory and use -U postgres and -p 5532 flags.
On 23 December 2015 at 20:19, Melvin Davidson <melvin6925@gmail.com> wrote:It's possible the restore is still building indexes.What does it show when you run this query?Where do I run this query? Do I stop the restore that is 'active'?
SELECT datname,
pid as pid,
client_addr,
usename as user,
query,
CASE WHEN waiting = TRUE
THEN 'BLOCKED'
ELSE 'no'
END as waiting,
query_start,
current_timestamp - query_start as duration
FROM pg_stat_activity
WHERE pg_backend_pid() <> pid
ORDER BY datname,
query_start;On Wed, Dec 23, 2015 at 2:14 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:09 AM, Killian Driscoll wrote:On 23 December 2015 at 20:07, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
On 12/23/2015 11:03 AM, Killian Driscoll wrote:
On 23 December 2015 at 16:02, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>> wrote:
On 12/23/2015 06:50 AM, Killian Driscoll wrote:
On 23 December 2015 at 15:47, Adrian Klaver
<adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the
command is
being found.
OK - --help on the 9.3 lists help options
In your original post you said you have a 9.3
instance and
a 9.4
instance.
>From your post I would say the 9.3 instance was
installed
by the
one click installer from EDB and the 9.4 from
Bitami, is
that correct?
Correct.
So do you know where the 9.4 binaries are installed?
If by binaries, you mean the program files they are
installed
C:\Bitnami\wappstack-5.5.30-0\postgresql\bin
Per previous posts you want, whenever possible, to us a newer
version of pg_dump to move a database from an older
version(9.3) to
a newer one(9.4). Therefore you should do your dump and restore
using the pg_dump.exe and pg_restore.exe from the Bitanami bin
directory. I would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out
irll_project
pg_restore -U postgres -p 5532 irll_project.out
It appeared to work with this method, but it has now been
running for
almost 4 hours with no result. The db is not that large (probably v.
small by most standards) and the .out file is ~200mb
What is running, the dump or the restore?
The restore - I can see the dump .out file that was created at 16hr in
the postgresql/bin folder
So how are you determining it is running and that it is not doing anything?
What does the Postgres log for the 9.4 instance show?
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
--
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
![](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif)
On 12/23/2015 11:17 AM, Killian Driscoll wrote:On 23 December 2015 at 20:14, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
So how are you determining it is running and that it is not doing
anything?
Since I ran the restore the windows shell has been 'active' with codes
lines running - I took that as being active.....!
So what do they say?
What does the Postgres log for the 9.4 instance show?
Where is the log - here Control Panel\System and Security\Administrative
Tools in event viewer or elsewhere?
My guess in the Bitnami directory tree under logs/ or something similar.
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
Do not stop the active restore.
Just run psql from the command shell in the Bitnami binary directory and use -U postgres and -p 5532 flags.On Wed, Dec 23, 2015 at 2:22 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:19, Melvin Davidson <melvin6925@gmail.com> wrote:It's possible the restore is still building indexes.What does it show when you run this query?Where do I run this query? Do I stop the restore that is 'active'?
SELECT datname,
pid as pid,
client_addr,
usename as user,
query,
CASE WHEN waiting = TRUE
THEN 'BLOCKED'
ELSE 'no'
END as waiting,
query_start,
current_timestamp - query_start as duration
FROM pg_stat_activity
WHERE pg_backend_pid() <> pid
ORDER BY datname,
query_start;
Server [localhost]:
Database [postgres]:
Port [5432]: 5532
Username [postgres]:
psql (9.3.4, server 9.4.4)
WARNING: psql major version 9.3, server major version 9.4.
Some psql features might not work.
WARNING: Console code page (850) differs from Windows code page (1252)
8-bit characters might not work correctly. See psql reference
page "Notes for Windows users" for details.
Type "help" for help.
postgres=# SELECT datname,
postgres-# pid as pid,
postgres-# client_addr,
postgres-# usename as user,
postgres-# query,
postgres-# CASE WHEN waiting = TRUE
postgres-# THEN 'BLOCKED'
postgres-# ELSE 'no'
postgres-# END as waiting,
postgres-# query_start,
postgres-# current_timestamp - query_start as duration
postgres-# FROM pg_stat_activity
postgres-# WHERE pg_backend_pid() <> pid
postgres-# ORDER BY datname,
postgres-# query_start;
datname | pid | client_addr | user |
query
| waiting | query_start | duration
--------------+------+-------------+----------+---------------------------------
--------------------------------------------------------------------------------
---+---------+----------------------------+--------------
irll_project | 8088 | 127.0.0.1 | postgres | SELECT defaclacl FROM pg_catalog
.pg_default_acl dacl WHERE dacl.defaclnamespace = 19228::oid AND defaclobjtype='
T' | no | 2015-12-23 17:37:18.295+01 | 02:46:37.17
postgres | 5084 | 127.0.0.1 | postgres | SELECT setting FROM pg_settings
WHERE name IN ('autovacuum', 'track_counts')
| no | 2015-12-23 17:37:02.469+01 | 02:46:52.996
(2 rows)
postgres=#
On Wed, Dec 23, 2015 at 2:14 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:09 AM, Killian Driscoll wrote:On 23 December 2015 at 20:07, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
On 12/23/2015 11:03 AM, Killian Driscoll wrote:
On 23 December 2015 at 16:02, Adrian Klaver
<adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>> wrote:
On 12/23/2015 06:50 AM, Killian Driscoll wrote:
On 23 December 2015 at 15:47, Adrian Klaver
<adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
So cd into:
C:\Program Files\PostgreSQL\9.3\bin
and try:
pg_dump --help
that will at least establish that the
command is
being found.
OK - --help on the 9.3 lists help options
In your original post you said you have a 9.3
instance and
a 9.4
instance.
>From your post I would say the 9.3 instance was
installed
by the
one click installer from EDB and the 9.4 from
Bitami, is
that correct?
Correct.
So do you know where the 9.4 binaries are installed?
If by binaries, you mean the program files they are
installed
C:\Bitnami\wappstack-5.5.30-0\postgresql\bin
Per previous posts you want, whenever possible, to us a newer
version of pg_dump to move a database from an older
version(9.3) to
a newer one(9.4). Therefore you should do your dump and restore
using the pg_dump.exe and pg_restore.exe from the Bitanami bin
directory. I would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out
irll_project
pg_restore -U postgres -p 5532 irll_project.out
It appeared to work with this method, but it has now been
running for
almost 4 hours with no result. The db is not that large (probably v.
small by most standards) and the .out file is ~200mb
What is running, the dump or the restore?
The restore - I can see the dump .out file that was created at 16hr in
the postgresql/bin folder
So how are you determining it is running and that it is not doing anything?
What does the Postgres log for the 9.4 instance show?
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
--Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
On 12/23/2015 11:27 AM, Killian Driscoll wrote: > On 23 December 2015 at 20:24, Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > On 12/23/2015 11:17 AM, Killian Driscoll wrote: > > On 23 December 2015 at 20:14, Adrian Klaver > <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > <mailto:adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>>> wrote: > > > > > > So how are you determining it is running and that it is not > doing > anything? > > Since I ran the restore the windows shell has been 'active' with > codes > lines running - I took that as being active.....! > > > So what do they say? > > If I 'slow down' the code by using the scroll on the right I can see > words from the db I recognise, but the rest is very long alphanumeric > characters. > > > > What does the Postgres log for the 9.4 instance show? > > Where is the log - here Control Panel\System and > Security\Administrative > Tools in event viewer or elsewhere? > > > My guess in the Bitnami directory tree under logs/ or something similar. > > > I can't see a log folder..... Not sure how you installed Bitnami, but here is quick reference showing file locations: https://wiki.bitnami.com/Components/PostgreSQL#Quick_reference_card -- Adrian Klaver adrian.klaver@aklaver.com
On 23 December 2015 at 20:24, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:17 AM, Killian Driscoll wrote:On 23 December 2015 at 20:14, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
So how are you determining it is running and that it is not doing
anything?
Since I ran the restore the windows shell has been 'active' with codes
lines running - I took that as being active.....!
So what do they say?If I 'slow down' the code by using the scroll on the right I can see words from the db I recognise, but the rest is very long alphanumeric characters.
What does the Postgres log for the 9.4 instance show?
Where is the log - here Control Panel\System and Security\Administrative
Tools in event viewer or elsewhere?
My guess in the Bitnami directory tree under logs/ or something similar.I can't see a log folder.....
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.com
--
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
![](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif)
It's usually located in<Bitnami dir>\data\pg_logBut if you have no errors in the postgresql log (after the restore completed), you should be fine.Since you never told us the info about whether you have a 32 or 64 bit system, how much memory, what processor speed, etc, it's hard to say how long it will take.But from your last reply, it looks like Postgres is finishing the restore by VACUUMing the database. That means it has to vacuum every table.You can rREDIRECT the output to a file! EG: psql -U postgres -p 5532 > your_output.txtthen use notepad to see the result.
--On Wed, Dec 23, 2015 at 2:27 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:24, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:17 AM, Killian Driscoll wrote:On 23 December 2015 at 20:14, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
So how are you determining it is running and that it is not doing
anything?
Since I ran the restore the windows shell has been 'active' with codes
lines running - I took that as being active.....!
So what do they say?If I 'slow down' the code by using the scroll on the right I can see words from the db I recognise, but the rest is very long alphanumeric characters.
What does the Postgres log for the 9.4 instance show?
Where is the log - here Control Panel\System and Security\Administrative
Tools in event viewer or elsewhere?
My guess in the Bitnami directory tree under logs/ or something similar.I can't see a log folder.....
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.comMelvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
On 23 December 2015 at 20:38, Melvin Davidson <melvin6925@gmail.com> wrote:It's usually located in<Bitnami dir>\data\pg_logBut if you have no errors in the postgresql log (after the restore completed), you should be fine.Since you never told us the info about whether you have a 32 or 64 bit system, how much memory, what processor speed, etc, it's hard to say how long it will take.But from your last reply, it looks like Postgres is finishing the restore by VACUUMing the database. That means it has to vacuum every table.You can rREDIRECT the output to a file! EG: psql -U postgres -p 5532 > your_output.txtthen use notepad to see the result.OK - I see the logs there - the last log was almost 12 hrs ago, so no recent one.
--On Wed, Dec 23, 2015 at 2:27 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:24, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:17 AM, Killian Driscoll wrote:On 23 December 2015 at 20:14, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
So how are you determining it is running and that it is not doing
anything?
Since I ran the restore the windows shell has been 'active' with codes
lines running - I took that as being active.....!
So what do they say?If I 'slow down' the code by using the scroll on the right I can see words from the db I recognise, but the rest is very long alphanumeric characters.
What does the Postgres log for the 9.4 instance show?
Where is the log - here Control Panel\System and Security\Administrative
Tools in event viewer or elsewhere?
My guess in the Bitnami directory tree under logs/ or something similar.I can't see a log folder.....
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.comMelvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
--
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
![](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif)
>OK - I see the logs there - the last log was almost 12 hrs ago, so no recent one.That's not very helpful. Depending on how you've configured the logging, PostgreSQL may only create one log file a day.
Conventional thinking is It's what is IN the log file that is important.
ERROR: syntax error at or near "1" at character 1
STATEMENT: 1 0106000020E61000000100000001030000000100000049000000A2EA743BD46B1DC0EC7756B43F1
On Wed, Dec 23, 2015 at 2:50 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:38, Melvin Davidson <melvin6925@gmail.com> wrote:It's usually located in<Bitnami dir>\data\pg_logBut if you have no errors in the postgresql log (after the restore completed), you should be fine.Since you never told us the info about whether you have a 32 or 64 bit system, how much memory, what processor speed, etc, it's hard to say how long it will take.But from your last reply, it looks like Postgres is finishing the restore by VACUUMing the database. That means it has to vacuum every table.You can rREDIRECT the output to a file! EG: psql -U postgres -p 5532 > your_output.txtthen use notepad to see the result.OK - I see the logs there - the last log was almost 12 hrs ago, so no recent one.
--On Wed, Dec 23, 2015 at 2:27 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:24, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:17 AM, Killian Driscoll wrote:On 23 December 2015 at 20:14, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
So how are you determining it is running and that it is not doing
anything?
Since I ran the restore the windows shell has been 'active' with codes
lines running - I took that as being active.....!
So what do they say?If I 'slow down' the code by using the scroll on the right I can see words from the db I recognise, but the rest is very long alphanumeric characters.
What does the Postgres log for the 9.4 instance show?
Where is the log - here Control Panel\System and Security\Administrative
Tools in event viewer or elsewhere?
My guess in the Bitnami directory tree under logs/ or something similar.I can't see a log folder.....
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.comMelvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
--Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
On 23 December 2015 at 20:59, Melvin Davidson <melvin6925@gmail.com> wrote:>OK - I see the logs there - the last log was almost 12 hrs ago, so no recent one.That's not very helpful. Depending on how you've configured the logging, PostgreSQL may only create one log file a day.
I didn't change a configuration, so it is how it came 'out of the box'Conventional thinking is It's what is IN the log file that is important.Apologies - I have looked, but what's in it doesn't appear to relate to the current pg_restore as it was logged many hours before so I didn't mention it, and its a 13mb file so I didn't attach it.One thing I see it says
ERROR: syntax error at or near "1" at character 1
STATEMENT: 1 0106000020E61000000100000001030000000100000049000000A2EA743BD46B1DC0EC7756B43F1with the latter part being similar to the alphanumeric I see currently running in the windows shell. This is all a bit above my pay grade as you've probably gathered....
On Wed, Dec 23, 2015 at 2:50 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:38, Melvin Davidson <melvin6925@gmail.com> wrote:It's usually located in<Bitnami dir>\data\pg_logBut if you have no errors in the postgresql log (after the restore completed), you should be fine.Since you never told us the info about whether you have a 32 or 64 bit system, how much memory, what processor speed, etc, it's hard to say how long it will take.But from your last reply, it looks like Postgres is finishing the restore by VACUUMing the database. That means it has to vacuum every table.You can rREDIRECT the output to a file! EG: psql -U postgres -p 5532 > your_output.txtthen use notepad to see the result.OK - I see the logs there - the last log was almost 12 hrs ago, so no recent one.
--On Wed, Dec 23, 2015 at 2:27 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:24, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:17 AM, Killian Driscoll wrote:On 23 December 2015 at 20:14, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
So how are you determining it is running and that it is not doing
anything?
Since I ran the restore the windows shell has been 'active' with codes
lines running - I took that as being active.....!
So what do they say?If I 'slow down' the code by using the scroll on the right I can see words from the db I recognise, but the rest is very long alphanumeric characters.
What does the Postgres log for the 9.4 instance show?
Where is the log - here Control Panel\System and Security\Administrative
Tools in event viewer or elsewhere?
My guess in the Bitnami directory tree under logs/ or something similar.I can't see a log folder.....
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.comMelvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
--Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
On 23 December 2015 at 20:59, Melvin Davidson <melvin6925@gmail.com> wrote:>OK - I see the logs there - the last log was almost 12 hrs ago, so no recent one.That's not very helpful. Depending on how you've configured the logging, PostgreSQL may only create one log file a day.
I didn't change a configuration, so it is how it came 'out of the box'Conventional thinking is It's what is IN the log file that is important.Apologies - I have looked, but what's in it doesn't appear to relate to the current pg_restore as it was logged many hours before so I didn't mention it, and its a 13mb file so I didn't attach it.One thing I see it says
ERROR: syntax error at or near "1" at character 1
STATEMENT: 1 0106000020E61000000100000001030000000100000049000000A2EA743BD46B1DC0EC7756B43F1with the latter part being similar to the alphanumeric I see currently running in the windows shell. This is all a bit above my pay grade as you've probably gathered....On Wed, Dec 23, 2015 at 2:50 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:38, Melvin Davidson <melvin6925@gmail.com> wrote:It's usually located in<Bitnami dir>\data\pg_logBut if you have no errors in the postgresql log (after the restore completed), you should be fine.Since you never told us the info about whether you have a 32 or 64 bit system, how much memory, what processor speed, etc, it's hard to say how long it will take.But from your last reply, it looks like Postgres is finishing the restore by VACUUMing the database. That means it has to vacuum every table.You can rREDIRECT the output to a file! EG: psql -U postgres -p 5532 > your_output.txtthen use notepad to see the result.OK - I see the logs there - the last log was almost 12 hrs ago, so no recent one.
--On Wed, Dec 23, 2015 at 2:27 PM, Killian Driscoll <killiandriscoll@gmail.com> wrote:On 23 December 2015 at 20:24, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 12/23/2015 11:17 AM, Killian Driscoll wrote:On 23 December 2015 at 20:14, Adrian Klaver <adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>> wrote:
So how are you determining it is running and that it is not doing
anything?
Since I ran the restore the windows shell has been 'active' with codes
lines running - I took that as being active.....!
So what do they say?If I 'slow down' the code by using the scroll on the right I can see words from the db I recognise, but the rest is very long alphanumeric characters.
What does the Postgres log for the 9.4 instance show?
Where is the log - here Control Panel\System and Security\Administrative
Tools in event viewer or elsewhere?
My guess in the Bitnami directory tree under logs/ or something similar.I can't see a log folder.....
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
<mailto:adrian.klaver@aklaver.com
<mailto:adrian.klaver@aklaver.com>>
--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
--
Adrian Klaver
adrian.klaver@aklaver.comMelvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
--Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
--
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
![](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif)
I was half awake early this AM and perused my email, and noted a fubar in one of the command sets shown to you but too sleepy to try and reply at the time, and now this thread is WAY too silly long to find it again, but I think someone neglected to put the database name on a pg_restore command. if you don't give pg_restore a dbname, it just spews the SQL out on the console, which is what it sounded like Killian may have described. yeah, this one from Adrian, at 7:02am PST (Z-0800) this morning.... > Per previous posts you want, whenever possible, to us a newer version > of pg_dump to move a database from an older version(9.3) to a newer > one(9.4). Therefore you should do your dump and restore using the > pg_dump.exe and pg_restore.exe from the Bitanami bin directory. I > would cd to the above directory and do: > > pg_dump -V > pg_restore -V > > to make sure the programs are found and are the 9.4 versions. > > Then do: > > pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project > > pg_restore -U postgres -p 5532 irll_project.out that last needs to have -d newdbname where newdbname has already been created, for instance, by... C:\Bitnami\wappstack-5.5.30-0\postgresql\bin\createdb -p 5532 -U postgres newdbname BEFORE you can restore to it.... anyways, this thread has gone on WAY too long, Killian needs to learn the basics of command line operations on MS Windows, which admittedly are rather klunky, but are quite outside the charter of the pgsql-general email list. p.s. please don't CC me answers, I get every email sent to the list, with the CC's I end up getting two of every one. -- john r pierce, recycling bits in santa cruz
On 12/23/2015 12:12 PM, John R Pierce wrote: > I was half awake early this AM and perused my email, and noted a fubar > in one of the command sets shown to you but too sleepy to try and reply > at the time, and now this thread is WAY too silly long to find it again, > but I think someone neglected to put the database name on a pg_restore > command. if you don't give pg_restore a dbname, it just spews the > SQL out on the console, which is what it sounded like Killian may have > described. > > > yeah, this one from Adrian, at 7:02am PST (Z-0800) this morning.... > >> Per previous posts you want, whenever possible, to us a newer version >> of pg_dump to move a database from an older version(9.3) to a newer >> one(9.4). Therefore you should do your dump and restore using the >> pg_dump.exe and pg_restore.exe from the Bitanami bin directory. I >> would cd to the above directory and do: >> >> pg_dump -V >> pg_restore -V >> >> to make sure the programs are found and are the 9.4 versions. >> >> Then do: >> >> pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project >> >> pg_restore -U postgres -p 5532 irll_project.out > > that last needs to have -d newdbname where newdbname has already > been created, for instance, by... Aah, my mistake. Yes you need to specify the database to get the restore to work properly. Also explains why there is nothing in the logs. > > C:\Bitnami\wappstack-5.5.30-0\postgresql\bin\createdb -p 5532 -U > postgres newdbname > > BEFORE you can restore to it.... > > > anyways, this thread has gone on WAY too long, Killian needs to learn > the basics of command line operations on MS Windows, which admittedly > are rather klunky, but are quite outside the charter of the > pgsql-general email list. > > > > > p.s. please don't CC me answers, I get every email sent to the list, > with the CC's I end up getting two of every one.\ FYI, you can go here: http://www.postgresql.org/mailpref/pgsql-general and set eliminatecc to have the listserver do that for you. > -- Adrian Klaver adrian.klaver@aklaver.com
On 12/23/2015 12:37 PM, Adrian Klaver wrote: >> p.s. please don't CC me answers, I get every email sent to the list, >> with the CC's I end up getting two of every one.\ > > FYI, you can go here: > > http://www.postgresql.org/mailpref/pgsql-general > > and set eliminatecc to have the listserver do that for you. except, its the one from the list that I want to keep in my archive. my filter isn't sophisticated enough to separate them (I'm just filtering on Subject contains: [GENERAL]) -- john r pierce, recycling bits in santa cruz
John R Pierce <pierce@hogranch.com> writes: >> FYI, you can go here: >> http://www.postgresql.org/mailpref/pgsql-general >> and set eliminatecc to have the listserver do that for you. > except, its the one from the list that I want to keep in my archive. > my filter isn't sophisticated enough to separate them (I'm just > filtering on Subject contains: [GENERAL]) Maybe drop messages that contain that *and* are not from the list bounce address, ie envelope sender isn't pgsql-general-owner...@postgresql.org ? Actually, rather than looking at the Subject: at all, you should look to see if pgsql-general@postgresql.org is in To: or cc:, and combine that with the wrong-sender filter. That would avoid dropping private replies. Reply-to-all is a sufficiently ingrained habit around here that there is exactly no chance people will do your filtering for you. The reasons for that are partly historical no doubt (the listserv used to be a lot less reliable/prompt than it is now), but the custom is established. regards, tom lane
On 12/23/2015 12:12 PM, John R Pierce wrote:I was half awake early this AM and perused my email, and noted a fubar
in one of the command sets shown to you but too sleepy to try and reply
at the time, and now this thread is WAY too silly long to find it again,
but I think someone neglected to put the database name on a pg_restore
command. if you don't give pg_restore a dbname, it just spews the
SQL out on the console, which is what it sounded like Killian may have
described.
yeah, this one from Adrian, at 7:02am PST (Z-0800) this morning....Per previous posts you want, whenever possible, to us a newer version
of pg_dump to move a database from an older version(9.3) to a newer
one(9.4). Therefore you should do your dump and restore using the
pg_dump.exe and pg_restore.exe from the Bitanami bin directory. I
would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project
pg_restore -U postgres -p 5532 irll_project.out
that last needs to have -d newdbname where newdbname has already
been created, for instance, by...
Aah, my mistake. Yes you need to specify the database to get the restore to work properly. Also explains why there is nothing in the logs.
C:\Bitnami\wappstack-5.5.30-0\postgresql\bin\createdb -p 5532 -U
postgres newdbname
BEFORE you can restore to it....
anyways, this thread has gone on WAY too long, Killian needs to learn
the basics of command line operations on MS Windows, which admittedly
are rather klunky, but are quite outside the charter of the
pgsql-general email list.
p.s. please don't CC me answers, I get every email sent to the list,
with the CC's I end up getting two of every one.\
FYI, you can go here:
http://www.postgresql.org/mailpref/pgsql-general
and set eliminatecc to have the listserver do that for you.
--
Adrian Klaver
adrian.klaver@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Attachment
On 12/24/2015 12:03 AM, Killian Driscoll wrote: > > > yeah, this one from Adrian, at 7:02am PST (Z-0800) this morning.... > > Per previous posts you want, whenever possible, to us a > newer version > of pg_dump to move a database from an older version(9.3) to > a newer > one(9.4). Therefore you should do your dump and restore > using the > pg_dump.exe and pg_restore.exe from the Bitanami bin > directory. I > would cd to the above directory and do: > > pg_dump -V > pg_restore -V > > to make sure the programs are found and are the 9.4 versions. > > Then do: > > pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project > > pg_restore -U postgres -p 5532 irll_project.out > > > that last needs to have -d newdbname where newdbname has already > been created, for instance, by... > > > Aah, my mistake. Yes you need to specify the database to get the > restore to work properly. Also explains why there is nothing in the > logs. > > > OK - with the inclusion of stating the dbname the restore works, but not > correctly: what is restored is 24 of 48 tables and 1 of 22 views from > one schema and no tables from the other schema. > > A log appeared at 0:08 last night (I'm at GMT +1), which I've attached. > Plus, I did the dump and restore again this morning and have attached > the text from the windows shell if that helps > Well the one from this morning shows(I did not look through whole thing) you restoring over existing database objects. I would say at this point the best thing you can do is get to a known state on the 9.4 cluster you want to dump to. I am assuming you are not doing anything with the database irll_project on the 9.4 server at this point, correct? If so, for the below keep track of exactly what you do and the order you do it, in case you need to post back here. 1) On the 9.4 server, while logged into another database on the server, say postgres do: DROP DATABASE irll_project; 2) Using the 9.4 version of pg_dump dump the 9.3 version of irll_project. 3) Using the 9.4 version of pg_restore restore irll_project to the 9.4 server. -- Adrian Klaver adrian.klaver@aklaver.com
Well the one from this morning shows(I did not look through whole thing) you restoring over existing database objects. I would say at this point the best thing you can do is get to a known state on the 9.4 cluster you want to dump to. I am assuming you are not doing anything with the database irll_project on the 9.4 server at this point, correct?On 12/24/2015 12:03 AM, Killian Driscoll wrote:
yeah, this one from Adrian, at 7:02am PST (Z-0800) this morning....
Per previous posts you want, whenever possible, to us a
newer version
of pg_dump to move a database from an older version(9.3) to
a newer
one(9.4). Therefore you should do your dump and restore
using the
pg_dump.exe and pg_restore.exe from the Bitanami bin
directory. I
would cd to the above directory and do:
pg_dump -V
pg_restore -V
to make sure the programs are found and are the 9.4 versions.
Then do:
pg_dump -Fc -p 5432 -U postgres -f irll_project.out irll_project
pg_restore -U postgres -p 5532 irll_project.out
that last needs to have -d newdbname where newdbname has already
been created, for instance, by...
Aah, my mistake. Yes you need to specify the database to get the
restore to work properly. Also explains why there is nothing in the
logs.
OK - with the inclusion of stating the dbname the restore works, but not
correctly: what is restored is 24 of 48 tables and 1 of 22 views from
one schema and no tables from the other schema.
A log appeared at 0:08 last night (I'm at GMT +1), which I've attached.
Plus, I did the dump and restore again this morning and have attached
the text from the windows shell if that helps
If so, for the below keep track of exactly what you do and the order you do it, in case you need to post back here.
1) On the 9.4 server, while logged into another database on the server, say postgres do:
DROP DATABASE irll_project;
2) Using the 9.4 version of pg_dump dump the 9.3 version of irll_project.
3) Using the 9.4 version of pg_restore restore irll_project to the 9.4 server.
--
Adrian Klaver
adrian.klaver@aklaver.com
Killian Driscoll <killiandriscoll@gmail.com> wrote: > It worked - thank you very much for your time. Great! > Regarding the file format used: I had used the pg_dump with .sql, but you > suggested .out. Is there a particular reason to use .out instead of .sql when > backing up? No, doesn't matter. Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds) "If I was god, I would recompile penguin with --enable-fly." (unknown) Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
On 12/29/2015 11:38 PM, Killian Driscoll wrote: > On 24 December 2015 at 18:33, Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > > > It worked - thank you very much for your time. > > Regarding the file format used: I had used the pg_dump with .sql, but > you suggested .out. Is there a particular reason to use .out instead of > .sql when backing up? I do that to distinguish between plain text dumps(*.sql) and custom format dumps(*.out) for myself. Postgres itself does not care about the extension, or if there is an extension at all. > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > -- Adrian Klaver adrian.klaver@aklaver.com