Re: Partial indexes instead of partitions

From: Leonardo F <m_lists(at)yahoo(dot)it>
To: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Partial indexes instead of partitions
Date: 2010-06-11 12:29:45
Message-ID: 461294.47994.qm@web29015.mail.ird.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> Could you please explain the reason to do so many
> partitions?

Because otherwise there would be tons of rows in each
partition, and randomly "updating" the index for that many
rows 2000 times per second isn't doable (the indexes
get so big that it would be like writing a multi-GB file
randomly)

> In case b) you will face a huge overhead related to necessity
> of
> checking all the data in the table every time new index is
> created

I would create the table with all the indexes already in; but only

the index related to the "current timestamp of the inserted row"
would be updated; the others wouldn't be touched.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sergey Konoplev 2010-06-11 12:39:56 Re: Partial indexes instead of partitions
Previous Message Sergey Konoplev 2010-06-11 11:54:47 Re: Partial indexes instead of partitions