I don't think I have used any new v8.4 feature, since I finally had my
first encounter with v8.4 this week.
What should i be looking for in the dump script?
Jason
On Thu, May 6, 2010 at 12:13 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Greg Smith <greg@2ndquadrant.com> writes:
>> Jason Tan Boon Teck wrote:
>>> I need to move some databases written in Psql v8.4 to the stable
>>> production server running v8.3. I tried pg_dump and pg_restore as well
>>> as PgAdmin3. I am unable to do so due to the backward
>>> incompatibility. Is there anyway to do this?
>
>> You can try connecting a 8.3 client to the 8.4 server, then running
>> pg_dump from that 8.3 client. That's a common approach for
>> dump/restore when moving forward a version, and it may resolve your
>> issue when moving backward one too. The 8.3 client shouldn't dump
>> anything the 8.3 server doesn't know how to restore.
>
> That's very likely to fail, and worse to do so silently, because 8.3
> pg_dump doesn't know what's different about 8.4 system catalogs.
>
> I think your only real recourse in this situation is to do a plain dump
> from the 8.4 server (with 8.4 pg_dump) and then manually edit the dump
> script to remove any 8.4-only syntax. If your application isn't actually
> using any 8.4-only features this should be a pretty trivial matter.
> If it is, then of course you have some work to do.
>
> regards, tom lane
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
--
Jason Tan Boon Teck
