Re: pg_upgrade: How to deal with toast

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade: How to deal with toast
Date: 2008-11-20 11:36:57
Message-ID: 49254BD9.1050001@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas napsal(a):

> It the new attribute is added to the end, the old tuples will be
> compatible as is. If there's no null bitmap (or it's shorter than
> expectd), attributes missing from a tuple are implicitly NULL. That's
> how we support ALTER TABLE ADD COLUMN without rewriting all the data.
>

Yeah, but better is to put int column before chunk data. It save space
(alignment). I prefer to put attno as a third column.

Zdenek

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-11-20 12:24:24 Autoconf, libpq and replacement function
Previous Message Grzegorz Jaskiewicz 2008-11-20 11:08:47 Re: Updated posix fadvise patch v19