<note to future>
To anyone reading this in the future, if you have problems importing a plain text database export, it is usually impossible to do:
psql -d some_dbase -f the_backup.sql. I don't know why. What works is doing 'cd ./the_files_directory', going INTO psql command line, then issuing '\i the_backup.sql', and it's really fast. 8 seconds for 128 mbyte file.
PS,do this as user 'postgres' on the system.
</note to future>
Probably, you were right, it was pg_dump. It says 'database dump' in the file at the top.
As far as which version it came from, that was 2 years ago, I couldn't tell you. And it doesn't say in the file.
I successfully imported it into 8.4.11.
The errors were always 'illegal command', 10s of thousands of them. As far as what I did 2 years ago, I can't remember 2 days ago, sorry about that ;-) Yes it is a plan text dump. I don't have huge databases yet, so to make it easier to go between versions, I use a text backup.
Hope that answers your questions.
Dennis Gearon
To anyone reading this in the future, if you have problems importing a plain text database export, it is usually impossible to do:
psql -d some_dbase -f the_backup.sql. I don't know why. What works is doing 'cd ./the_files_directory', going INTO psql command line, then issuing '\i the_backup.sql', and it's really fast. 8 seconds for 128 mbyte file.
PS,do this as user 'postgres' on the system.
</note to future>
Probably, you were right, it was pg_dump. It says 'database dump' in the file at the top.
As far as which version it came from, that was 2 years ago, I couldn't tell you. And it doesn't say in the file.
I successfully imported it into 8.4.11.
The errors were always 'illegal command', 10s of thousands of them. As far as what I did 2 years ago, I can't remember 2 days ago, sorry about that ;-) Yes it is a plan text dump. I don't have huge databases yet, so to make it easier to go between versions, I use a text backup.
Hope that answers your questions.
Never, ever approach a computer saying or even thinking "I will just do this quickly."
From: Adrian Klaver <adrian.klaver@xxxxxxxxx>
To: Dennis Gearon <gearond@xxxxxxxxxxxxx>
Cc: pgsql-general@xxxxxxxxxxxxxx
Sent: Thu, September 27, 2012 6:34:31 AM
Subject: Re: problem with recreating database with export
On 09/26/2012 08:44 PM, Dennis Gearon wrote:
> It turns out that I had made the export from psql, a text based export.
I just do not see how you can be exporting schema definitions from within psql. I still say pg_dump is involved somewhere.
>
> So I read that it was actually needing to be imported using '\i
> filename_in_local_directory'
What about the other questions I posed?:
What versions of Postgres are you using?
Are you going from one version to another?
Are you in fact talking about doing a plain text pg_dump?
New questions:
To be clear what are the actual commands used to create the export?
Also what are the actual errors you get when trying to import the data?
> Dennis Gearon
-- Adrian Klaver
adrian.klaver@xxxxxxxxx
From: Adrian Klaver <adrian.klaver@xxxxxxxxx>
To: Dennis Gearon <gearond@xxxxxxxxxxxxx>
Cc: pgsql-general@xxxxxxxxxxxxxx
Sent: Thu, September 27, 2012 6:34:31 AM
Subject: Re: problem with recreating database with export
On 09/26/2012 08:44 PM, Dennis Gearon wrote:
> It turns out that I had made the export from psql, a text based export.
I just do not see how you can be exporting schema definitions from within psql. I still say pg_dump is involved somewhere.
>
> So I read that it was actually needing to be imported using '\i
> filename_in_local_directory'
What about the other questions I posed?:
What versions of Postgres are you using?
Are you going from one version to another?
Are you in fact talking about doing a plain text pg_dump?
New questions:
To be clear what are the actual commands used to create the export?
Also what are the actual errors you get when trying to import the data?
> Dennis Gearon
-- Adrian Klaver
adrian.klaver@xxxxxxxxx
