Re: [WIP]Vertical Clustered Index (columnar store extension) - take2

From: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [WIP]Vertical Clustered Index (columnar store extension) - take2
Date: 2025-01-15 14:43:46
Message-ID: 86b18f04-4feb-4c89-af91-65f40dd81404@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

07.10.2024 17:53, Aya Iwata (Fujitsu) wrote:
> Hi All,
>
> Suggestions
>
> ==========
>
> When analyzing real-time data collected by PostgreSQL,
>
> it can be difficult to tune the current PostgreSQL server for
> satisfactory performance.
>
> Therefore, we propose Vertical Clustered Indexing (VCI), an in-memory
> column store function that holds data in a state suitable for business
> analysis and is also expected to improve analysis performance.

I just don't get, why it should be "in-memory"? All the same things you
describe further, but storing in paged index on-disk with caching
through shared_buffers - why this way it wouldn't work?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Banck 2025-01-15 14:59:04 Re: Purpose of wal_init_zero
Previous Message Robert Haas 2025-01-15 14:40:42 Re: Eager aggregation, take 3