Re: On columnar storage - Mailing list pgsql-hackers

From Michael Nolan
Subject Re: On columnar storage
Date
Msg-id CAOzAquLEEA=uLe38qfdUSDQHuUipaC78bo4hB5WUVLn4UV+A1Q@mail.gmail.com
Whole thread Raw
In response to On columnar storage  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: On columnar storage  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers


On Thu, Jun 11, 2015 at 7:03 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
We hope to have a chance to discuss this during the upcoming developer
unconference in Ottawa.  Here are some preliminary ideas to shed some
light on what we're trying to do.


I've been trying to figure out a plan to enable native column stores
(CS or "colstore") for Postgres.  Motivations:

* avoid the 32 TB limit for tables
* avoid the 1600 column limit for tables
* increased performance

Are you looking to avoid all hardware-based limits, or would using a 64 bit row pointer be possible?  That would give you 2^64 or 1.8 E19 unique rows over whatever granularity/uniqueness you use (per table, per database, etc.)
--
Mike Nolan.

pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: Hash index creation warning
Next
From: Peter Geoghegan
Date:
Subject: Re: Further issues with jsonb semantics, documentation