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

From Rod Taylor
Subject Re: (A) native Windows port
Date
Msg-id 1026256796.54899.2.camel@jester
Whole thread Raw
In response to Re: (A) native Windows port  (Lamar Owen <lamar.owen@wgcr.org>)
Responses Re: (A) native Windows port
List pgsql-hackers
On Tue, 2002-07-09 at 19:09, Lamar Owen wrote:
> On Tuesday 09 July 2002 04:17 pm, Hannu Krosing wrote:
> > On Tue, 2002-07-09 at 22:10, Lamar Owen wrote:
> > > The pre-upgrade script is run in an environment that isn't robust enough
> > > to handle that.  What if you run out of disk space during the dump?
> 
> > You can either check beforehand or abort and delete the offending
> > dumpfile.
> 
> And what if you have enough disk space to do the dump, but then that causes 
> the OS upgrade to abort because there wasn't enough space left to finish 
> upgrading (larger packages, perhaps)?  The system's hosed, and it's our 
> fault.

What normally happens when you have low amounts of free diskspace and
attempt to upgrade the system?

On FreeBSD (portupgrade) it rolls back any changes it was attempting.  I
don't know other systems to be able to say.


Postgresql may require more diskspace to upgrade than most packages, 
but if the tools cannot fail cleanly it is already a problem that needs
to be addressed.



pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: (A) native Windows port
Next
From: Lamar Owen
Date:
Subject: Re: (A) native Windows port