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

From Rod Taylor
Subject Re: (A) native Windows port
Date
Msg-id 1026258858.54899.24.camel@jester
Whole thread Raw
In response to Re: (A) native Windows port  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
> Can the ports system take into account the space required for a dumpfile?? :-)

It cheats by keeping a backup of the old version -- makes an installable
package out of the currently installed version.  This is removed once
the package has been successfully upgraded (including dependencies).

On failure, it rolls back any packages (and those that depend on it) to
prior versions it backed up and continues on trying to upgrade other
parts of the system which don't depend on the rolled back portion.

Portupgrade regularly upgrades part of the system if the ports tree is
broken, won't build (architecture issues), couldn't download XYZ item,
or has run into other problems.  PostgreSQL in this case simply wouldn't
get upgraded with everything else -- reporting errors at the end.  That
said, Postgresql also may no longer work after the upgrade -- but I
guess thats what the 'test' mode is used to prevent.








pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: (A) native Windows port
Next
From: "Arthur@LinkLine.com"
Date:
Subject: Re: pg_access