Re: On columnar storage
| От | Michael Nolan |
|---|---|
| Тема | Re: On columnar storage |
| Дата | |
| Msg-id | CAOzAquLEEA=uLe38qfdUSDQHuUipaC78bo4hB5WUVLn4UV+A1Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | On columnar storage (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: On columnar storage
|
| Список | 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 по дате отправления: