From: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
---|---|
To: | Kevin Heflin <kheflin(at)shreve(dot)net> |
Cc: | "PGSQL-General (E-mail)" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] editing file after pg_dump |
Date: | 1999-03-18 19:56:32 |
Message-ID: | 36F15A70.5087BD2C@rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Kevin Heflin wrote:
>
> I've run pg_dump on a database, which I've done many times before, to
> backup and then restore databases.
>
> However, this time before I restore the database, I'm wanting to edit one
> of the datatypes before I restore the data. As soon as I open up the file
> then save it, regardless of actually making any changes.. the restore will
> fail whenever it gets to the point of inserting the data.
>
> I'm guessing it's choking because whatever text editor I'm using is hosing
> the fields with long entries... I've tried opening the file with vi, pico,
> and Homesite on a WindowsNT box..
>
> Any suggestions on how to get around this?
you might try dumping the schema and data separately:
pg_dump -a yourdb >yourdb.data
pg_dump -s yourdb >yourdb.schema
then edit the schema without touching the data, then
psql newdb <yourdb.schema
psql newdb <yourdb.data
For speed, you may want to split the schema where the indeces are
created, and run that after the data load.
psql newdb <yourdb.schema.tables
psql newdb <yourdb.data
psql newdb <yourdb.schema.indices
HTH,
Ross
--
Ross J. Reedstrom, Ph.D., <reedstrm(at)rice(dot)edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005
From | Date | Subject | |
---|---|---|---|
Next Message | Sascha Schumann | 1999-03-18 19:58:31 | Re: [SQL] Vacuum |
Previous Message | Kevin Heflin | 1999-03-18 19:52:23 | Re: [GENERAL] editing file after pg_dump |