From: | Michael Nolan <htfoot(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: On columnar storage |
Date: | 2015-06-12 22:07:01 |
Message-ID: | CAOzAquLEEA=uLe38qfdUSDQHuUipaC78bo4hB5WUVLn4UV+A1Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 11, 2015 at 7:03 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2015-06-12 22:16:48 | Re: Further issues with jsonb semantics, documentation |
Previous Message | Thom Brown | 2015-06-12 22:00:54 | Re: Hash index creation warning |