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 15:50:32
Message-ID: 2449.1227196232@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:
> 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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2008-11-20 16:13:23 Re: Hot Standby (commit fest version - v5)
Previous Message Grzegorz Jaskiewicz 2008-11-20 15:40:39 Re: Re: [COMMITTERS] pgsql: Silence compiler warning about ignored return value.