You are right again. I don't want to make permanet changes for this one-time problem.
Yes I find a way to
Use pg_restore to make a text dump script, and then edit that, and then load it into your newer server.
- pg_restore can output to file not only database. I will edit this file. Thanks.
Kaloyan
Tom Lane wrote:
Kaloyan Iliev Iliev <[EMAIL PROTECTED]> writes:
But as I say the file with copy commands contains
[EMAIL PROTECTED]@[EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@COPY "tracking_base" FROM stdin;
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@I^,[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@epay_requests_archive
^@
things like that. So how can I change this.
Use pg_restore to make a text dump script, and then edit that, and then load it into your newer server.
For me it will be easier to change the schema (which is in normal text format). To remove the field from the base table and to add it at the end of each table that inherits the base table.
[ shrug... ] If you want to make a permanent change to work around this one-time problem ...
regards, tom lane
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
