Re: [PATCH] Space reservation v02 - Mailing list pgsql-hackers

From Euler Taveira de Oliveira
Subject Re: [PATCH] Space reservation v02
Date
Msg-id 49846E3A.8070906@timbira.com
Whole thread Raw
In response to Re: [PATCH] Space reservation v02  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: [PATCH] Space reservation v02  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
Simon Riggs escreveu:
> On Tue, 2009-01-27 at 13:06 +0100, Zdenek Kotala wrote:
> 
>> Space reservation MUST TO be implemented if we
>> want to have 8.4->8.5 upgrade. 
> 
> Why not just add a few dummy columns onto each catalog table? If we need
> space to expand a row we can just drop one of the dummy columns from the
> new catalog definition.
> 
The problem is: how much space do we need at each catalog table? Suppose that
after 2 releases we need x + 1 bytes per tuple but we only foresaw x bytes; so we need to deprecate support for this
versionand advise DBA to run
 
pg_upgrade two times. I prefer a solution where we know beforehand the size
per tuple so when we're rewriting we could use this information to upgrade.


--  Euler Taveira de Oliveira http://www.timbira.com/


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: expected collation and ctype on windows?
Next
From: Magnus Hagander
Date:
Subject: Re: mingw check hung