From: | Goran Thyni <goran(at)bildbasen(dot)se> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Cc: | Mattias Kregert <matti(at)algonet(dot)se> |
Subject: | Re: [HACKERS] An easier way to upgrade (Was: Lots 'o patches) |
Date: | 1998-06-02 14:04:18 |
Message-ID: | 35740662.A12290FC@bildbasen.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mattias Kregert wrote:
> How about making a file specifying what to do when upgrading from one
> version of pg to another? Then a program, let's call it 'pgconv', would
> read this file and do the conversions from the old to the new format
> using pg_dump and psql and/or some other helper programs.
I think what is needed is a replication program, since pgsql uses
socket comunication it is quiet easy to run 2 concurrent systems
say one each of 6.3.2 and 6.4 and copy beteewn them at run-time.
The easiest way would be to use dump&load but as David pointed out in
a case where dump&load takes 20 hours it means 20 hours downtime unless
we want inconsistent data (data inserted/updated while copying).
A smarter replication would make the downtime shorter since most data
would be upto date and only latest changes need to be transfer during
"update downtime".
Such a mechanism would be even more useful for other proposes like
clustering/backup/redundancy etc.
Has anyone looked as this?
The only thing I have seen is the Mariposa project which seems to be
somewhat overkill for most applications.
--
---------------------------------------------
Göran Thyni, sysadm, JMS Bildbasen, Kiruna
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 1998-06-02 14:11:00 | Re: [HACKERS] An easier way to upgrade (Was: Lots 'o patches) |
Previous Message | Thomas G. Lockhart | 1998-06-02 13:56:17 | Re: [HACKERS] Current sources? |