Re: Column storage positions - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: Column storage positions
Date
Msg-id E1539E0ED7043848906A8FF995BDA57901CAF70E@m0143.s-mxs.net
Whole thread Raw
In response to Re: Column storage positions  ("Phil Currier" <pcurrier@gmail.com>)
Responses Re: Column storage positions  (Andrew Dunstan <andrew@dunslane.net>)
Re: Column storage positions  (Kris Jurka <books@ejurka.com>)
List pgsql-hackers
> > In any case I think it's foolish not to tackle both issues at once.
> > We know we'd like to have both features and we know that
> all the same
> > bits of code need to be looked at to implement either.
>
> I guess I disagree with that sentiment.  I don't think it's
> necessary to bundle these two features together, even if some
> analysis will be duplicated between them, since they are
> completely distinct in a functional sense and will touch
> different places in the code.

I fully agree with Phil here.

And I also see a lot of unhappiness from users of system tables
when column numbers all over the system tables would not be logical
column
positions any more.

Andreas



pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas ADI SD"
Date:
Subject: Re: HOT for PostgreSQL 8.3
Next
From: Markus Schiltknecht
Date:
Subject: Re: [Monotone-devel] Re: SCMS question