Yea, we have never supported loading newer dumps into older servers. We do support the opposite, though.
--------------------------------------------------------------------------- Tobias Brox wrote: > > The following bug has been logged online: > > Bug reference: 1468 > Logged by: Tobias Brox > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.0.0 > Operating system: Linux, gentoo > Description: psql_dump is not backward compatible > Details: > > I have a situation where my peers is using PG 7.4.6, and they are pretty > pissed off at me for using PG 8.0 - the DB dumps are incompatible. The > command I use for generating the dump is "pg_dump -Oa NBET". > > I don't have version 7.4.6 installed myself, so I cannot reproduce this > reliably on my own. > > We use serial primary keys, the problem reported by my peers is that PG > 7.4.6 needs an "update sequence" on all the primary keys. The old data dump > outputs lines on this form: > > SELECT pg_catalog.setval('user_group_id_seq', 5, False); > > PG 8.0 swallows the old data without problems, so I suppose it's needed with > a switch for backword compatibility there. > > I tried pg_dump with the parameters "OaD" (make full "insert"-statements, > should be compatible with anything), but this was rejected by my peers. > > I think the problem should be reproducable with the information above, if > not I can try install PG 7.4.6 > to create some comparable dumps with PG 8.0 and PG 7.4.6. > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings