From: | Bosco Rama <postgres(at)boscorama(dot)com> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Upgrading databases |
Date: | 2009-11-11 18:58:43 |
Message-ID: | 4AFB0963.9080608@boscorama.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-interfaces |
Mark Richardson wrote:
> Sorry if this is in the wrong list, but this is the closest I could find...
>
> I have a 8.2.4 database and I installed 8.3.7 and tried using the same
> /pgsql/data/base directory and got an error about incompatiblity.
>
> The database currently has billions of records but it's sparsely populated.
> It took about 4 months to just populate the original database and I REALLY
> don't want to do that again.
>
> Is there a conversion routine to change the files themselves? I know I can
> dump and reload - but that takes large disk space and time. Any other way
> around?
There is no 'in-situ' DB upgrade between major updates from what I can
tell. There is, however, an alternative to the 'dump to disk' approach
which is to pipe the dump from the old DB to the new DB as outlined in
the migration guide here:
<http://www.postgresql.org/docs/8.3/static/migration.html>
HTH.
Bosc.
From | Date | Subject | |
---|---|---|---|
Next Message | David Kerr | 2009-11-11 19:01:41 | Re: Postgres Clustering Options |
Previous Message | Kevin Kempter | 2009-11-11 18:51:42 | Re: Upgrading databases |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2009-11-14 15:28:55 | Re: Upgrading databases |
Previous Message | Kevin Kempter | 2009-11-11 18:51:42 | Re: Upgrading databases |