Skip site navigation (1) Skip section navigation (2)

Re: Column storage positions

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Phil Currier <pcurrier(at)gmail(dot)com>
Cc: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Column storage positions
Date: 2007-04-02 01:47:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Phil Currier wrote:
> I haven't done much with it since February, largely because my
> available free time evaporated.  But I do intend to get back to it
> when I have a chance.  But you're right, the storage position stuff
> I've worked on is completely independent from display positions, and
> certainly wouldn't prevent that being added separately.

I agree with this comment from Tom last time it was discussed:

> 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.

Just tackling the side of the problem that interests you is probably not 
the ideal way to go.



In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-04-02 04:11:08
Subject: Re: Macros for typtype (was Re: Arrays of Complex Types)
Previous:From: Phil CurrierDate: 2007-04-02 00:44:52
Subject: Re: Column storage positions

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group