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

From Lev Kokotov
Subject Use Postgres as a column store by creating one table per column
Date
Msg-id CAPwLVyJJ_ePn7O3PoMjSTJ64w=0RY2vGu4BfHRG58krC1Gkdcw@mail.gmail.com
Whole thread Raw
Responses Re: Use Postgres as a column store by creating one table per column  (Justin Pryzby <pryzby@telsasoft.com>)
Re: Use Postgres as a column store by creating one table per column  (Stephen Frost <sfrost@snowman.net>)
Re: Use Postgres as a column store by creating one table per column  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
List pgsql-performance
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.

Thanks!

Best,
Lev

pgsql-performance by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Temporarily very slow planning time after a big delete
Next
From: Justin Pryzby
Date:
Subject: Re: Use Postgres as a column store by creating one table per column