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

From Jan Wieck
Subject Re: (A) native Windows port
Date
Msg-id 3D21B012.D6D34E53@Yahoo.com
Whole thread Raw
In response to Re: (A) native Windows port  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Responses Re: (A) native Windows port  (Lamar Owen <lamar.owen@wgcr.org>)
Re: (A) native Windows port  ("Matthew T. O'Connor" <matthew@zeut.net>)
List pgsql-hackers
Christopher Kings-Lynne wrote:
> 
> > > It would all work out of the box and would do wonderful things for the
> > > Postgres community.
> >
> > I like this idea, but let me just bring one little issue to note: are you
> > going to handle upgrades, and if so, how?  How are you going to
> > do a major
> > version upgrade?
> 
> Well, the easiest way would be to get them to uninstall the old version
> first, but I'm sure it can be worked out.  Perhaps even we shouldn't
> overwrite the old version anyway?

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. 


Jan

-- 

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: regress/results directory problem
Next
From: Thomas Lockhart
Date:
Subject: Re: regress/results directory problem