I am using postgresql 8.1.3 on redhat, and trying to use partitioned
tables to manage a multi-terabyte table. I've created the parent table
and the child tables.

If I want to add an index, does it matter if I index the parent or the
collection of children? I can't find a discussion of the pros or cons
on this in the documentation.

On 16.08.2012 19:48, Greg Hennessy wrote:
To me this seems pretty clear: indexes are not automatically inherited
and the master table is usually empty => index child tables. It's all
in the docs:

http://www.postgresql.org/docs/8.1/s...NHERIT-CAVEATS
http://www.postgresql.org/docs/8.1/s...titioning.html

Cheers

robert

--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

On Thu, 16 Aug 2012 17:48:53 +0000, Greg Hennessy wrote:

In Postgres, parent table is usually empty. You can only index child
tables. And there are no global indexes, it isn't possible to have a
unique index across all the tables.



--
Mladen Gogala
http://mgogala.freehostia.com

On 2012-08-16, Greg Hennessy <greg.hennessy (AT) cox (DOT) net> wrote:
Upgrade! But seriously, upgrade. 8.1.23 at a minumum.

you need to add it to each of the children that will benefit from
having it. usually this means all of them.

indexing the parent will bave no possitive effect, the database knows it's
really empty

you're going to want to turn constraint excluusion "on" if you haven't
alredy. (8.1 doesn't have a 'partition' setting for constraint exclusiin)
upgrade to someting newer like 9.1 for improved performance.

--
⚂⚃ 100% natural

--- Posted via news://freenews.netfront.net/ - Complaints to news (AT) netfront (DOT) net ---