Excerpts from Tom Lane's message of mar dic 20 22:23:36 -0300 2011:
>
> Alvaro Herrera writes:
> > Excerpts from Tom Lane's message of mar dic 20 18:24:29 -0300 2011:
> >> You do *not* want to store either of the latter two numbers in
> >> parse-time Var nodes, because then you can't rearrange c
Excerpts from Simon Riggs's message of mié dic 21 15:53:20 -0300 2011:
> On Wed, Dec 21, 2011 at 1:42 PM, Alvaro Herrera
> wrote:
>
> > This one I'm not sure about at all:
> >
> >> * "very large number of columns" for statistical data sets where we
> >> automatically vertically partition the hea
On Wed, Dec 21, 2011 at 1:42 PM, Alvaro Herrera
wrote:
> This one I'm not sure about at all:
>
>> * "very large number of columns" for statistical data sets where we
>> automatically vertically partition the heap when faced with large
>> numbers of column definitions
We currently have pg_attribu
Excerpts from Simon Riggs's message of mié dic 21 09:44:04 -0300 2011:
> Sounds great.
>
> While you're doing this, I'd like to think about future requirements,
> to see if that changes anything.
>
> Having a unique logical column id is a great thing because it allows
> the physical storage to
On Tue, Dec 20, 2011 at 9:47 PM, Alvaro Herrera
wrote:
>> > The idea described there by Tom, and upon which I formed a vague
>> > implementation plan in my head, is that I was to look for all uses of
>> > an "attnum", and then replace it by either "attlognum" (i.e. the
>> > user-visible sort iden
Alvaro Herrera writes:
> Excerpts from Tom Lane's message of mar dic 20 18:24:29 -0300 2011:
>> You do *not* want to store either of the latter two numbers in
>> parse-time Var nodes, because then you can't rearrange columns without
>> having to update stored rules. But it might be useful to decr
Excerpts from Tom Lane's message of mar dic 20 18:24:29 -0300 2011:
> Alvaro Herrera writes:
> > I've been trying to implement the holy grail of decoupling
> > logical/physical column sort order representation, i.e., the feature
> > that lets the server have one physical order, for storage compac
Alvaro Herrera writes:
> I've been trying to implement the holy grail of decoupling
> logical/physical column sort order representation, i.e., the feature
> that lets the server have one physical order, for storage compactness,
> and a different "output" order that can be tweaked by the user. Thi
