Re: Postgres for a "data warehouse", 5-10 TB

Поиск
Список
Период
Сортировка
Искать
От
Marti Raudsepp
Тема
Re: Postgres for a "data warehouse", 5-10 TB
Дата
Msg-id
CABRT9RAJvq0bzBnqtEzc=80H7oYPYC4LggKWZOYcDbRRMnskJA@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Postgres for a "data warehouse", 5-10 TB Igor Chudov <ichudov@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Stephen Frost <sfrost@snowman.net>
Re: Postgres for a "data warehouse", 5-10 TB Igor Chudov <ichudov@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Stephen Frost <sfrost@snowman.net>
Re: Postgres for a "data warehouse", 5-10 TB Ondrej Ivanič <ondrej.ivanic@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Claudio Freire <klaussfreire@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Stephen Frost <sfrost@snowman.net>
Re: Postgres for a "data warehouse", 5-10 TB Andy Colson <andy@squeakycode.net>
Re: Postgres for a "data warehouse", 5-10 TB Claudio Freire <klaussfreire@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Shaun Thomas <sthomas@peak6.com>
Re: Postgres for a "data warehouse", 5-10 TB Scott Marlowe <scott.marlowe@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Igor Chudov <ichudov@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Andy Colson <andy@squeakycode.net>
Re: Postgres for a "data warehouse", 5-10 TB Marti Raudsepp <marti@juffo.org>
Re: Postgres for a "data warehouse", 5-10 TB Shaun Thomas <sthomas@peak6.com>
Re: Postgres for a "data warehouse", 5-10 TB Scott Marlowe <scott.marlowe@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Shaun Thomas <sthomas@peak6.com>
Re: Postgres for a "data warehouse", 5-10 TB Marti Raudsepp <marti@juffo.org>
Re: Postgres for a "data warehouse", 5-10 TB Scott Marlowe <scott.marlowe@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Shaun Thomas <sthomas@peak6.com>
Re: Postgres for a "data warehouse", 5-10 TB Scott Marlowe <scott.marlowe@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Robert Klemme <shortcutter@googlemail.com>
Re: Postgres for a "data warehouse", 5-10 TB Andy Colson <andy@squeakycode.net>
Re: Postgres for a "data warehouse", 5-10 TB Robert Klemme <shortcutter@googlemail.com>
Re: Postgres for a "data warehouse", 5-10 TB Gianni Ciolli <gianni.ciolli@2ndquadrant.it>
Re: Postgres for a "data warehouse", 5-10 TB Marti Raudsepp <marti@juffo.org>
Re: Postgres for a "data warehouse", 5-10 TB Robert Klemme <shortcutter@googlemail.com>
Re: Postgres for a "data warehouse", 5-10 TB Marti Raudsepp <marti@juffo.org>
Re: Postgres for a "data warehouse", 5-10 TB Stefan Keller <sfkeller@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Scott Marlowe <scott.marlowe@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Robert Klemme <shortcutter@googlemail.com>
Re: Postgres for a "data warehouse", 5-10 TB Igor Chudov <ichudov@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Robert Klemme <shortcutter@googlemail.com>
Re: Postgres for a "data warehouse", 5-10 TB Claudio Freire <klaussfreire@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Igor Chudov <ichudov@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Andy Colson <andy@squeakycode.net>
Re: Postgres for a "data warehouse", 5-10 TB Claudio Freire <klaussfreire@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Shaun Thomas <sthomas@peak6.com>
Re: Postgres for a "data warehouse", 5-10 TB Ogden <lists@darkstatic.com>
Re: Postgres for a "data warehouse", 5-10 TB J Sisson <sisson.j@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB J Sisson <sisson.j@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB pasman pasmański <pasman.p@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Igor Chudov <ichudov@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Scott Marlowe <scott.marlowe@gmail.com>
Re: Postgres for a "data warehouse", 5-10 TB Robert Klemme <shortcutter@googlemail.com>
Re: Postgres for a "data warehouse", 5-10 TB Scott Marlowe <scott.marlowe@gmail.com>
On Tue, Sep 13, 2011 at 00:26, Robert Klemme  wrote:
> In the case of PG this particular example will work:
> 1. TX inserts new PK row
> 2. TX tries to insert same PK row => blocks
> 1. TX commits
> 2. TX fails with PK violation
> 2. TX does the update (if the error is caught)

That goes against the point I was making in my earlier comment. In
order to implement this error-catching logic, you'll have to allocate
a new subtransaction (transaction ID) for EVERY ROW you insert. If
you're going to be loading billions of rows this way, you will invoke
the wrath of the "vacuum freeze" process, which will seq-scan all
older tables and re-write every row that it hasn't touched yet. You'll
survive it if your database is a few GB in size, but in the terabyte
land that's unacceptable. Transaction IDs are a scarce resource there.

In addition, such blocking will limit the parallelism you will get
from multiple inserters.

Regards,
Marti
В списке pgsql-performance по дате отправления
От: Anthony Presley
Дата:
От: Robert Klemme
Дата:
FAQ