| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, HACKERS <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: (A) native Windows port |
| Date: | 2002-07-02 16:04:05 |
| Message-ID: | 200207021204.05329.matthew@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> The question is not how to replace some .EXE and .DLL files or modify
> something in the registry. The question is what to do with the existing
> databases in the case of a catalog version change. You have to dump and
> restore.
pg_upgrade?
Otherwise: no upgrades persay, but you can intall the new version into a new
directory and then have an automated pg_dump / restore between the old and
the new. This would require a lot of disk space, but I don't see any other
clean way to automate it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | frbn | 2002-07-02 16:17:39 | Re: Does postgreSQL have distributed database management |
| Previous Message | Lamar Owen | 2002-07-02 15:41:04 | Re: (A) native Windows port |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2002-07-02 17:56:48 | ignor ethis ... |
| Previous Message | Lamar Owen | 2002-07-02 15:41:04 | Re: (A) native Windows port |