Postgres and really huge tables

Поиск
Список
Период
Сортировка
От Brian Hurt
Тема Postgres and really huge tables
Дата
Msg-id 45AFD927.9050605@janestcapital.com
обсуждение исходный текст
Ответ на Re: RES: Priority to a mission critical transaction  (Ron Mayer <rm_pg@cheapcomplexdevices.com>)
Ответы Re: [pgsql-advocacy] Postgres and really huge tables  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Postgres and really huge tables  (Scott Marlowe <smarlowe@g2switchworks.com>)
Re: [pgsql-advocacy] Postgres and really huge tables  (Chris Mair <chris@1006.org>)
Re: Postgres and really huge tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Postgres and really huge tables  (Gavin Sherry <swm@alcove.com.au>)
Re: Postgres and really huge tables  ("Merlin Moncure" <mmoncure@gmail.com>)
Список pgsql-performance
Is there any experience with Postgresql and really huge tables?  I'm
talking about terabytes (plural) here in a single table.  Obviously the
table will be partitioned, and probably spread among several different
file systems.  Any other tricks I should know about?

We have a problem of that form here.  When I asked why postgres wasn't
being used, the opinion that postgres would "just <explicitive> die" was
given.  Personally, I'd bet money postgres could handle the problem (and
better than the ad-hoc solution we're currently using).  But I'd like a
couple of replies of the form "yeah, we do that here- no problem" to
wave around.

Brian



В списке pgsql-performance по дате отправления:

Предыдущее
От: "Jeremy Haile"
Дата:
Сообщение: Re: Autoanalyze settings with zero scale factor
Следующее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: [pgsql-advocacy] Postgres and really huge tables