From: Stephen Frost <sfrost@snowman.net>
To: Lev Kokotov <lev.kokotov@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Use Postgres as a column store by creating one table per column
Date: Fri, 24 May 2019 15:38:15 -0400
Message-ID: <20190524193815.GE2480@tamriel.snowman.net> (raw)
In-Reply-To: <CAPwLVyJJ_ePn7O3PoMjSTJ64w=0RY2vGu4BfHRG58krC1Gkdcw@mail.gmail.com>
References: <CAPwLVyJJ_ePn7O3PoMjSTJ64w=0RY2vGu4BfHRG58krC1Gkdcw@mail.gmail.com>
Greetings,
* Lev Kokotov (lev.kokotov@gmail.com) wrote:
> Is it efficient to use Postgres as a column store by creating one table per
> column?
Short answer is no, not in a traditional arrangement, anyway. The tuple
overhead would be extremely painful. It's possible to improve on that,
but it requires sacrificing what the tuple header gives you- visibility
information, along with some other things. The question will be if
that's acceptable or not.
> 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.
The page size in PG is 8k, not 16MB.
Thanks,
Stephen
Attachments:
[application/pgp-signature] signature.asc (818B, ../20190524193815.GE2480@tamriel.snowman.net/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sfrost@snowman.net, lev.kokotov@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Use Postgres as a column store by creating one table per column
In-Reply-To: <20190524193815.GE2480@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox