Tom,
> That sounds good, but there are corner cases where it wouldn't work ---
> consider a page containing a single maximum-length tuple.
Certainly any mature upgrade-in-place tool will require a "checker" which you
run first which determines if you have a prohibitive corner case.
Besides, I
Heikki Linnakangas wrote:
Since we're discussing upgrades, let me summarize the discussions we had
over dinner in Ottawa for the benefit of all:
Thanks for summary.
As before, someone just needs to step up and do it.
I'm now working on proposal. I hope that it will ready soon.
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> * Page format changes that grow data size are problematic, because there
> can be pages that can't be expanded to the new format because there's
> not enough space. However, it would be possible to write a pre-upgrade
> program to look for the pro
Since we're discussing upgrades, let me summarize the discussions we had
over dinner in Ottawa for the benefit of all:
* pg_migrator is a sound approach to handling catalog changes.
* Handling any page format change that doesn't grow the space taken by
data is straightforward. Note that all 8.
Andrew Sullivan wrote:
On Wed, Jun 20, 2007 at 12:34:21PM -0400, Robert Treat wrote:
FWIW pg_migrator is a pretty good swing at an in-place upgrade tool for
8.1->8.2. Unfortunately until the PGDG decides that in-place upgrade is a
constraint their willing to place on development, I see them a
On Wed, Jun 20, 2007 at 12:34:21PM -0400, Robert Treat wrote:
> FWIW pg_migrator is a pretty good swing at an in-place upgrade tool for
> 8.1->8.2. Unfortunately until the PGDG decides that in-place upgrade is a
> constraint their willing to place on development, I see them a good
> chicken/eg
On Tuesday 19 June 2007 10:15, Tom Lane wrote:
> Zdenek Kotala <[EMAIL PROTECTED]> writes:
> > I'm little bit confused when we introduce new page layout version? I
> > expect that new version become with changes with pageheader, tuple
> > header or data encoding (varlen/TOAST ...). But in case when
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> I'm little bit confused when we introduce new page layout version? I
> expect that new version become with changes with pageheader, tuple
> header or data encoding (varlen/TOAST ...). But in case when there is
> new data type internal implementation, t
Simon Riggs wrote:
The objections to applying this patch originally were:
1. it changes on-disk format (we've done this, so argument is void)
I'm little bit confused when we introduce new page layout version? I
expect that new version become with changes with pageheader, tuple
header or dat
