Re: pg_upgrade project status

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade project status
Date: 2008-11-10 23:39:50
Message-ID: 200811102339.mAANdo517050@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala wrote:
> In the last week community made decision about pg_upgrade project and its
> implementation. I would like to try summarize this conclusion and I add other
> topic which should be finished for 8.4.
>
> Convert on read has been selected as a good way, because it is not invasive and
> does not limit fresh database. But, this way needs core modification which
> allows to do online in-place upgrade. It means no online in-place upgrade to 8.4
> will be implemented. Sorry about that, but we need move forward and there is not
> easy way without core modification to do it.
>
> As I mentioned manytimes before there are two major issues with convert on read
> and one small issue.
>
> 1) Data does not fit on the new page. It will be solve by pre-upgrade check
> which reserve space on each page, before upgrade.

Rather than specifying free space as an amount, I was thinking of having
a boolean like 'ready_for_upgrade' and the system internally would know
how much free space for each page and tuple.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-11-10 23:59:38 Re: SQL5 budget
Previous Message Bruce Momjian 2008-11-10 23:32:33 Re: gram.y=>preproc.y