| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | Decibel! <decibel(at)decibel(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Zdenek Kotala" <Zdenek(dot)Kotala(at)sun(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Page space reservation (pgupgrade) |
| Date: | 2008-11-10 01:17:34 |
| Message-ID: | 36e682920811091717g65346b45ie02d1cc3a47d3d4a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Nov 9, 2008 at 7:55 PM, Decibel! <decibel(at)decibel(dot)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.
--
Jonah H. Harris, Senior DBA
myYearbook.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-11-10 01:18:31 | Re: Reducing some DDL Locks to ShareLock |
| Previous Message | Tom Lane | 2008-11-10 01:06:51 | Re: [PATCH] Recreate Missing WAL Directories (from TODO) |