From: | "Derricutt, Mark" <DerricuttM(at)pbworld(dot)com> |
---|---|
To: | pgsql-general(at)hub(dot)org |
Subject: | Problems with pg_dump... |
Date: | 2000-01-17 21:40:09 |
Message-ID: | 93314B6256A5D211BE8B006097B950271791D3@NZAM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi, I've got a few problems with pg_dump that I was wondering if you guys
could help me out with.
I have my local database on my machine, and a database on a remote webserver
and I was wanting to move -one- table from my local db to the remote.
So I used "pg_dump -f mytable.sql -t cdcollection derricuttm" to dump just
that one table and uploaded it to my remote machine.
When I tried to import the table into the other database, it failed because
the used sequence didn't exist. Shouldn't the -t option in pg_dump include
everything to recreate that particular table, such as its sequences?
Anyway, I added those lines to mytable.sql and reran it, and now get:
COPY "cdcollection" FROM stdin;
ERROR: Bad date external representation '07-26-1999'
PQendcopy: resetting connection
CREATE UNIQUE INDEX "cdcollection_cd_id_key" on "cdcollection" using btree (
"cd_id" "int4 _ops" );
CREATE
EOF
The respective versions of PostgreSQL are:
Local: 6.4 (I could only find the version number in PG_VERSION)
Remote: [PostgreSQL 6.5.1 on i586-pc-linux-gnu, compiled by gcc 2.7.2.3]
Have there been some changes in the way dates are handled between 6.4 anf
6.5.1? Or should I be doing something different?
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Ed Bras | 2000-01-17 21:52:28 | Comments in postgres ? |
Previous Message | Charles Tassell | 2000-01-17 20:39:35 | Re: [GENERAL] cgi with postgres |