Re: Redhat 7 and PgSQL

From: teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=)
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Efrain Caro <betsemes(at)hotmail(dot)com>, Jeff Hoffmann <jeff(at)propertykey(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Redhat 7 and PgSQL
Date: 2000-10-01 15:30:28
Message-ID: xuyaecok297.fsf@hoser.devel.redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:

> Trond Eivind Glomsrød writes:
>
> > > %preupgrade
> > > pg_dumpall >somewhere
>
> > 1) You don't know that postgresql is running. It probably isn't.
>
> Then start it.

That may not be possible, and wouldn't handle the possibility of it
not starting.

> > 2) You don't know that you have the diskspace to do that.
>
> Changing from one storage format to another always requires 2x space
> (although a text dump is usually smaller than the internal
> representation).

That depends on how you manipulate the on-disk format, but right now,
a problem is you have to do this before upgrading. Having a separate
tool going from one on-disk format to another and possibly failing
because of lack of disk space is OK - as long you can run it later
when you've added more space or point at a place with enough space
etc.

> And you're not going to get the storage format to not
> ever change again. :-)

With some thought and design for adding future capabities, perhaps it
could be possible?

--
Trond Eivind Glomsrød
Red Hat, Inc.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Enrico Comini 2000-10-01 16:03:52 BACK & RELOAD
Previous Message Fernando Lobo 2000-10-01 15:05:02 universities using postgresql