pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: s.caillet@free.fr
To: pgsql-performance@postgresql.org
Subject: Partitions number limitation ?
Date: Wed, 03 Sep 2008 12:00:22 +0200
Message-ID: <1220436022.48be603606137@imp.free.fr> (raw)

Hi !

To improve our software insert datas performance, we have decided to use
partition architecture in our database. It works well for the following volume :
45 main tables and 288 inherited daughter tables for each, that is a total of
12960 partitions.

I have some trouble now with another customer's database with the following
volume : 87 main tables and 288 tables for each, that is 25056 partitions.

Is there some kind of limit in postgresql about the number of partitions ? Do
you know some tuning in the conf files to improve postgresql management of so
many tables ? I have already used different tablespaces, one for each main table
and its 288 partitions.

I have many datas to insert into these tables (that is ten or hundred of
thousands every five minutes for each main group). Do you think it can be done
with a hardware raid 0 SATA disk (it's the case today ...) ?

Thank you all for help.

Best regards

Sylvain Caillet



view thread (3+ messages)  latest in thread

Message-ID: <1220436022.48be603606137@imp.free.fr>
Permalink:  ../1220436022.48be603606137@imp.free.fr/
Also on:    postgresql.org/message-id/1220436022.48be603606137@imp.free.fr

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: s.caillet@free.fr
  Subject: Re: Partitions number limitation ?
  In-Reply-To: <1220436022.48be603606137@imp.free.fr>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox