Path: csiph.com!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.databases.postgresql Subject: Re: index on a partitioned table Date: Fri, 17 Aug 2012 11:11:18 +0200 Lines: 23 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 77d7Qpjm5xSoXfUl5gd2OAOA6d+kUrvx8O/BMoBuy7ANXmZtBxqd+XcJXnSptc318= Cancel-Lock: sha1:HjLzP4UFOV6erTHF0qVPa36tS0A= User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 In-Reply-To: Xref: csiph.com comp.databases.postgresql:406 On 16.08.2012 19:48, Greg Hennessy wrote: > 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. 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/static/ddl-inherit.html#DDL-INHERIT-CAVEATS http://www.postgresql.org/docs/8.1/static/ddl-partitioning.html Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/