Partitioning: indexes, tables and FKs

From: Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Partitioning: indexes, tables and FKs
Date: 2010-02-02 12:26:34
Message-ID: 3eff28921002020426v15f64504l638354194abf1191@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all.

I'd like to understand how partitioning (actually table inheritance) works when
the number of tables grows in the order of thousands.
In my case, all child tables inherit also the indexes from the master
one (as well as constraints).

1. How will change the performances in the case a relevant number of
the child tables (10%) needs to
be included in the actual query? Do the needed time and resource grow
linearly (or what)?

2. How will work a PK on the master table in regards to the child tables?

3. Will a FK reference to the master table's PK be "redirected" to the
proper child table?

--
Vincenzo Romano
NotOrAnd Information Technologies
NON QVIETIS MARIBVS NAVTA PERITVS

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Schuchardt 2010-02-02 12:33:36 JOIN Record returning Function
Previous Message Gavin Mu 2010-02-02 12:05:47 Re: Can LISTEN/NOTIFY deal with more than 100 every second?