Search Postgresql Archives

Partitioning: indexes, tables and FKs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux