Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XYY9v-0003AM-RX for pgsql-admin@arkaria.postgresql.org; Mon, 29 Sep 2014 10:26:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XYY9v-0005Uo-A2 for pgsql-admin@arkaria.postgresql.org; Mon, 29 Sep 2014 10:26:23 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XYY9u-0005Uh-1l for pgsql-admin@postgresql.org; Mon, 29 Sep 2014 10:26:22 +0000 Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XYY9q-000489-84 for pgsql-admin@postgresql.org; Mon, 29 Sep 2014 10:26:19 +0000 Received: by mail-wi0-f169.google.com with SMTP id hi2so4266582wib.4 for ; Mon, 29 Sep 2014 03:26:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:reply-to:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=CKlCC4LTc6PeqPIM9i83nxP0fvezZyMjJ4TJ08fxxwk=; b=yn4lFPoYzrVtGD4g5YlONRbkaNBpBN2E19AsBDrsg1QrjxlAzW81MpH29MKH5cjVQg k1iuj1iA9p4pU6DWNSQpxlGV3LhX6WSB9Z6mGYn/8W6IeZBHw8PDeeW2PKm0bCM2L9GC rbS4OLruA+bC4QnqDzydC0L8UTglpjjEmmIqeKSy0LQJ0NuuoSgUKKIqpqrP5Zwj0usd 2YxNnSQlIFwFXzunoe0q3CfHa2ENZTv6n1q5LH53JvGp6evfE+isK1Cs2GS/vu02tA8f 2Rf8TihI56O5aWtvWqT5DzTvURGb9udTgojNIBIiD4fQ2y7jpNDu0uHJUHGqGnczvyZg wNvw== X-Received: by 10.194.103.200 with SMTP id fy8mr1833245wjb.123.1411986375403; Mon, 29 Sep 2014 03:26:15 -0700 (PDT) Received: from [192.168.1.15] (84.125.145.40.dyn.user.ono.com. [84.125.145.40]) by mx.google.com with ESMTPSA id f3sm11180273wiz.18.2014.09.29.03.26.13 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Mon, 29 Sep 2014 03:26:14 -0700 (PDT) Message-ID: <1411986372.3518.9.camel@enterprisedb01> Subject: Re: The tables partitioning affects the indexes? From: jaime soler Reply-To: jaime.soler@gmail.com To: DrakoRod Cc: pgsql-admin@postgresql.org Date: Mon, 29 Sep 2014 12:26:12 +0200 In-Reply-To: <1411680008162-5820572.post@n5.nabble.com> References: <1411680008162-5820572.post@n5.nabble.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -0.9 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org El jue, 25-09-2014 a las 14:20 -0700, DrakoRod escribió: > Hi everybody! > > I have a huge table that we need partitioning, partitioning rule is a > attribute date every 4 months. > > My Master table have a many indexes. I need create indexes (with the same > indexes the master table) in the inherits tables? or this no affects > functionality of the indexes? > > Best regards. > > Thanks! Reference: http://www.postgresql.org/docs/9.3/static/tutorial-inheritance.html "Note: Although inheritance is frequently useful, it has not been integrated with unique constraints or foreign keys, which limits its usefulness. See Section 5.8 for more detail." I think, you should create index in the child tables. > > > > -- > View this message in context: http://postgresql.1045698.n5.nabble.com/The-tables-partitioning-affects-the-indexes-tp5820572.html > Sent from the PostgreSQL - admin mailing list archive at Nabble.com. > > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin