Re: [HACKERS] upgrading to 6.4 from 6.3 - Mailing list pgsql-hackers

From Vadim Mikheev
Subject Re: [HACKERS] upgrading to 6.4 from 6.3
Date
Msg-id 35E9F773.74150FC9@krs.ru
Whole thread Raw
In response to upgrading to 6.4 from 6.3  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] upgrading to 6.4 from 6.3  (Bruce Momjian <maillist@candle.pha.pa.us>)
List 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

pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] Release 6.4
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] flock patch breaks things here