This sounds like a dangerous line to walk, to me. If the schemas for the two database systems are diverging, then trying to synchronize them is sure to have problems. I do not think that there is any miracle cure (using PostgreSQL or any other database system).
If you know of a sure subset of tables that are guaranteed not to change, then perhaps you can create a table by table script for those. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:pgsql-general- > [EMAIL PROTECTED] On Behalf Of Petr > Sent: Tuesday, December 27, 2005 4:00 PM > To: pgsql-general@postgresql.org > Subject: Re: [GENERAL] Detaching database > > OK. > > I'm try to explain my problems. My customer have Postgre server with any > older version of my DB (without any new or modified views, functions etc.) > and when i create export (in pgAdmin3), then pg_dump makes a SQL script. > Ok. > It's nice, but when i'm trying to run this script on customer's machine, > then i have many errors, because any views are not in his database, and > script trying to drop it. When i'm set to don't make drop functions (in > export), then i have other errors, with existing views (view allready > exists). > > Petr > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
