Re: Use Postgres as a column store by creating one table per column

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Use Postgres as a column store by creating one table per column
Date: 2019-05-25 03:55:52
Message-ID: 71cff455-6b4d-f969-5fd8-9b77c9a2c298@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Ancoron Luciferis 2019-05-25 13:45:53 UUID v1 optimizations...
Previous Message Stephen Frost 2019-05-24 19:38:15 Re: Use Postgres as a column store by creating one table per column