Re: t_self as system column

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: t_self as system column
Date: 2010-07-07 17:29:04
Message-ID: 1278523544-sup-4241@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Robert Haas's message of mar jul 06 17:24:21 -0400 2010:
> On Tue, Jul 6, 2010 at 5:18 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

> > In any case, having a mutable logical column
> > position is the feature that's been most requested.
>
> I think that's true. But the physical storage position would give us
> a performance benefit, by allowing us to try to avoid useless
> alignment padding.

That's true too. I intend to look at both problems simultaneously, i.e.
decoupling the current attnum in three columns as previously discussed;
as Tom says, I think it'll end up being less work than attacking them
separately. However, I will not attempt to include optimizations such
as avoiding padding, in the first patch, just the possibility that it is
added later.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-07-07 18:31:35 Re: cvs to git migration - keywords
Previous Message Robert Haas 2010-07-07 16:40:10 Re: cvs to git migration - keywords