Re: (A) native Windows port - Mailing list pgsql-hackers

From Dann Corbit
Subject Re: (A) native Windows port
Date
Msg-id D90A5A6C612A39408103E6ECDD77B82920D046@voyager.corporate.connx.com
Whole thread Raw
In response to (A) native Windows port  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
On generic recovery...

What is wrong with this strategy...

0. Put the database in single user mode.

1. Dump the Schema, with creation order properly defined, and with all
constraints written to a separate file.  (IOW, one file contains the
bare tables with no index, constraint or trigger stuff, and the other
contains all the RI stuff.)

2. Dump the tables (one by one) to text files with "copy"

3. Create a new database in a new location.

4. Feed it the bare table schema

5. Pump in the table data using "copy" from the saved text files

6. Run the RI script to rebuild index, trigger, PKey, FKey, etc.

I find that is the most trouble free way to do it with most DBMS
systems.

Am attempted dump from DBMS X.Y and a load to DBMS (X+1).Y is always a
pile of trouble waiting to happen -- no matter what the system is.




pgsql-hackers by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: (A) native Windows port
Next
From: Manfred Koizar
Date:
Subject: Page type and version