pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Zdenek Kotala <Zdenek.Kotala@Sun.COM>
To: Jonah H. Harris <jonah.harris@gmail.com>
Cc: Decibel! <decibel@decibel.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: WIP: Page space reservation (pgupgrade)
Date: Mon, 10 Nov 2008 08:52:19 +0100
Message-ID: <4917E833.7040409@sun.com> (raw)
In-Reply-To: <36e682920811091717g65346b45ie02d1cc3a47d3d4a@mail.gmail.com>
References: <491619D2.2090602@sun.com>
	<29590.1226192897@sss.pgh.pa.us>
	<36e682920811081835s5b2b07f1uf849b1d058ff80f5@mail.gmail.com>
	<CCF3CD20-1EC9-4DED-88BC-24A00735C74E@decibel.org>
	<36e682920811091717g65346b45ie02d1cc3a47d3d4a@mail.gmail.com>

Jonah H. Harris napsal(a):
> On Sun, Nov 9, 2008 at 7:55 PM, Decibel! <decibel@decibel.org> wrote:
>> On Nov 8, 2008, at 8:35 PM, Jonah H. Harris wrote:
>>> That's my question.  Why is this needed at all?
>> I suspect this is to deal with needing to reserve space in a cluster that
>> you're planning on upgrading to a new version that would take more space,
>> but I think the implementation is probably too simplistic.
> 
> Well, if that's what it is, I think it's a fairly poor design
> decision.  When I upgrade Oracle, SQL Server, or MySQL, I don't need
> to plan the amount of free space in my blocks a year or more before an
> upgrade.  In fact, I don't have to plan it at all... it's completely
> handled by the in-place upgrade.

It will be handled by PostgreSQL as well. The patch is about mechanism and 
configuration which will be used by in-place upgrade without any user activity. 
Only what user will have to do is run pg_upgrade_prepare() or something like 
this and when database will be ready then user can do upgrade.

		Zdenek





view thread (11+ messages)  latest in thread

Message-ID: <4917E833.7040409@sun.com>
Permalink:  ../4917E833.7040409@sun.com/
Also on:    postgresql.org/message-id/4917E833.7040409@sun.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: Zdenek.Kotala@Sun.COM, jonah.harris@gmail.com, decibel@decibel.org, tgl@sss.pgh.pa.us
  Subject: Re: WIP: Page space reservation (pgupgrade)
  In-Reply-To: <4917E833.7040409@sun.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox