Re: Diagonal storage model

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: Marko Tiikkaja <marko(at)joh(dot)to>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Diagonal storage model
Date: 2018-04-02 12:21:13
Message-ID: F26CA0AB-F793-4CF5-B10B-B3AAE60EB7E6@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 2 апр. 2018 г., в 16:57, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> написал(а):
> On Mon, Apr 2, 2018 at 3:49 AM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
>>
>> I'm a little worried about the fact that even with this model we're still
>> limited to only two dimensions. That's bound to cause problems sooner or
>> later.
> How about a 3D storage model, whose first dimension gives horizontal
> view, second provides vertical or columnar view and third one provides
> diagonal view. It also provides capability to add extra dimensions to
> provide additional views like double diagonal view. Alas! it all
> collapses since I was late to the party.

BTW, MDX expression actually provides mulitidimensional result. They have COLUMNS, ROWS, PAGES, SECTIONS, CHAPTERS, and AXIS(N) for those who is not satisfied with named dimensions.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2018-04-02 12:26:48 Re: [HACKERS] Add support for tuple routing to foreign partitions
Previous Message David Rowley 2018-04-02 12:03:15 Re: [HACKERS] path toward faster partition pruning