Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] An easier way to upgrade (Was: Lots 'o patches)

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Goran Thyni <goran(at)bildbasen(dot)se>
Cc: pgsql-hackers(at)postgreSQL(dot)org, Mattias Kregert <matti(at)algonet(dot)se>
Subject: Re: [HACKERS] An easier way to upgrade (Was: Lots 'o patches)
Date: 1998-06-02 14:11:00
Message-ID: Pine.BSF.3.96.980602101027.12843E-100000@hub.org (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, 2 Jun 1998, Goran Thyni wrote:

> 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.

	Someone had scripts for this that they were going to submit, but I
never heard further on it :(



In response to

pgsql-hackers by date

Next:From: Thomas G. LockhartDate: 1998-06-02 14:12:43
Subject: Re: [HACKERS] An easier way to upgrade (Was: Lots 'o patches)
Previous:From: Goran ThyniDate: 1998-06-02 14:04:18
Subject: Re: [HACKERS] An easier way to upgrade (Was: Lots 'o patches)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group