Re: pg_upgrade: How to deal with toast

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 18:29:13
Message-ID: 200811201829.mAKITDS27567@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala wrote:
> Tom Lane napsal(a):
> > Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> >> Heikki Linnakangas napsal(a):
> >>> Perhaps we should just add the new attid attribute to the toast table,
> >>> but mark it as nullable?
> >
> >> Hmm, It seems to me as a good idea.
> >
> > 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.

Once we have the 'require free space' capability in a major Postgres
release, can't we use that to make space for the new TOAST field we will
need?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2008-11-20 18:34:52 Re: pg_upgrade: How to deal with toast
Previous Message Bruce Momjian 2008-11-20 18:21:59 Re: TODO list request: FK to unique expression indexes