Re: Very large tables

Поиск
Список
Период
Сортировка
Искать
От
Grzegorz Jaśkiewicz
Тема
Re: Very large tables
Дата
Msg-id
2f4958ff0811280803o6849d83fjaeed7a4b69aa8586@mail.gmail.com
Ответ на
Re: Very large tables (Alvaro Herrera)
Список
Дерево обсуждения
Very large tables "William Temperley" <willtemperley@gmail.com>
Re: Very large tables Simon Riggs <simon@2ndQuadrant.com>
Re: Very large tables "William Temperley" <willtemperley@gmail.com>
Re: Very large tables Alvaro Herrera <alvherre@commandprompt.com>
Re: Very large tables "Grzegorz Jaśkiewicz" <gryzman@gmail.com>
Re: Very large tables "William Temperley" <willtemperley@gmail.com>
Re: Very large tables Alvaro Herrera <alvherre@commandprompt.com>
Re: Very large tables "Grzegorz Jaśkiewicz" <gryzman@gmail.com>
Re: Very large tables Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Very large tables Scara Maccai <m_lists@yahoo.it>


On Fri, Nov 28, 2008 at 3:48 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
William Temperley escribió:

> I've been asked to store a grid of 1.5 million geographical locations,
> fine. However, associated with each point are 288 months, and
> associated with each month are 500 float values (a distribution
> curve), i.e. 1,500,000 * 288 * 500 = 216 billion values :).
>
> So a 216 billion row table is probably out of the question. I was
> considering storing the 500 floats as bytea.

What about a float array, float[]?
you seriously don't want to use bytea to store anything, especially if the datatype matching exists in db of choice.
also, consider partitioning it :)

Try to follow rules of normalization, as with that sort of data - less storage space used, the better :)
And well, I would look for a machine with rather fast raid storage :) (and spacious too).



--
GJ
В списке pgsql-general по дате отправления
От: Adrian Klaver
Дата:
От: Ioana Danes
Дата:
FAQ