Re: (A) native Windows port

From: Rod Taylor <rbt(at)zort(dot)ca>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: Hannu Krosing <hannu(at)tm(dot)ee>, Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, HACKERS <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: (A) native Windows port
Date: 2002-07-09 23:54:17
Message-ID: 1026258858.54899.24.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general 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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message ljb 2002-07-10 00:42:13 Re: Frontend/backend protocol: authentication
Previous Message Bob Puff@NLE 2002-07-09 23:49:58 Converting from .MDB Access to PostgreSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Arthur@LinkLine.com 2002-07-10 00:35:18 Re: pg_access
Previous Message Lamar Owen 2002-07-09 23:40:55 Re: (A) native Windows port