Re: Use Postgres as a column store by creating one table per column - Mailing list pgsql-performance

From Mark Kirkwood
Subject Re: Use Postgres as a column store by creating one table per column
Date
Msg-id 71cff455-6b4d-f969-5fd8-9b77c9a2c298@catalyst.net.nz
Whole thread Raw
In response to Use Postgres as a column store by creating one table per column  (Lev Kokotov <lev.kokotov@gmail.com>)
List pgsql-performance
On 22/05/19 4:28 PM, Lev Kokotov wrote:
> Is it efficient to use Postgres as a column store by creating one 
> table per column?
>
> I would query it with something like `[...] UNION SELECT value AS 
> <table> FROM <table> WHERE value = <value> UNION [...]` to build a row.
>
> I'm thinking since Postgres stores tables in continuous blocks of 16MB 
> each (I think that's the default page size?) I would get efficient 
> reads and with parallel queries I could benefit from multiple cores.
>
>
Take a look at Zedstore, which is a column store built to plug into v12 
storage layer:

https://www.postgresql.org/message-id/CALfoeiuF-m5jg51mJUPm5GN8u396o5sA2AF5N97vTRAEDYac7w%40mail.gmail.com




pgsql-performance by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Use Postgres as a column store by creating one table per column
Next
From: Ancoron Luciferis
Date:
Subject: UUID v1 optimizations...