Re: pg_upgrade: How to deal with toast

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade: How to deal with toast
Date: 2008-11-20 20:16:54
Message-ID: 7249.1227212214@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> Tom Lane napsal(a):
>> No, it's a really horrid idea. Nullable attributes complicate the C
>> code, and what in the world are we buying with it anyway? Just decide
>> what the field should contain and put it in there.

> The problem what we try to solve is to perform this change during upgrade from
> 8.3->8.4. Extra value is a problem because it requires extra space and there is
> not free space. It is temporal solution(hack) for 8.3->8.4.

Solution of what? The original concern you had was about
TOAST_MAX_CHUNK_SIZE changing from 8.3 to 8.4. If that's a problem then
it has to be solved anyway, and the solution has to involve being able
to push some chunks off-page to make room. If it's not a problem then
let's just leave the toast representation as-is till later.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-20 20:23:01 Re: Autoconf, libpq and replacement function
Previous Message Tom Lane 2008-11-20 20:08:24 Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value.