| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Emmanuel Charpentier <charpent(at)bacbuc(dot)dyndns(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [Fwd: Backporting parts of databases from a 7.3 server to 7.2 : How ?] |
| Date: | 2003-02-04 08:18:40 |
| Message-ID: | 11156.1044346720@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Emmanuel Charpentier <charpent(at)bacbuc(dot)dyndns(dot)org> writes:
> However, this does *not* work between a 7.3-generated dump and a 7.2
> production server. The archiver complaints of an 'unknown archive format :
> "0"' (I'm quoting this from the top of my head : my production server is
> not reachable from the place I'm writing this).
In general, dumps from newer versions make use of SQL features that are
not in older versions; so it's more or less hopeless to expect backwards
compatibility of dumps. I'm not sure why pg_dump's archive header
format changed, but even without that you'd be facing SQL-level
compatibility issues.
You could perhaps have some success by dumping as a text-format dump
(not -Fc or -Ft) and then editing the resulting file to dumb the SQL
down to 7.2's level.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-02-04 11:23:13 | Re: MOVE LAST: why? |
| Previous Message | Emmanuel Charpentier | 2003-02-04 07:25:28 | [Fwd: Backporting parts of databases from a 7.3 server to 7.2 : How ?] |