Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] upgrading to 6.4 from 6.3

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] upgrading to 6.4 from 6.3
Date: 1998-08-31 01:08:03
Message-ID: 35E9F773.74150FC9@krs.ru (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian wrote:
> 
> Here is the last thing I think I promised for 6.4.  It is a script that
> will allow 6.3.* users to upgrade to 6.4 without reloading all their
> data.
> 
> It works by copying the user tables/index files to a backup directory,
> destroying and recreating the database, then using the
> pg_dump/pg_dumpall output to re-create the tables and indexes, without
> the COPY commands.  It then moves the table/index files back into the
> directory.

But how about pg_log & pg_variable ?
Shouldn't nextOid, nextXid and transaction commit/abort infos
be restored ?

> 
> If it works and people like it, I will write up a manual page, and
> mention it so people can use it.
> 
> I am not sure how to preserve the database owner because I need to
> drop/recreate the database.  Any ideas?
> 
> Vadim, I assume you did not change anything in the table or index
> structure.  You mentioned an index change, but I do not think you made
> it, did you?

No, I didn't.

Vadim

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 1998-08-31 02:34:40
Subject: Re: [HACKERS] flock patch breaks things here
Previous:From: The Hermit HackerDate: 1998-08-31 01:00:12
Subject: Re: [HACKERS] Release 6.4

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group