Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRMi6-00015B-6n for pgsql-docs@arkaria.postgresql.org; Thu, 16 May 2019 20:10:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hRMi4-0004Fx-DJ for pgsql-docs@arkaria.postgresql.org; Thu, 16 May 2019 20:10:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRMi4-0004Fn-2o for pgsql-docs@lists.postgresql.org; Thu, 16 May 2019 20:10:36 +0000 Received: from mail-qt1-x841.google.com ([2607:f8b0:4864:20::841]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRMi0-0007ES-Uc for pgsql-docs@lists.postgresql.org; Thu, 16 May 2019 20:10:35 +0000 Received: by mail-qt1-x841.google.com with SMTP id z19so5415993qtz.13 for ; Thu, 16 May 2019 13:10:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=a+sBHMOHJhrkJD+T2wbQ+6/KzOArTZmtd+Y1DntHMH0=; b=oWBoBb/fZ8yKbVM3Sn6PEfeQiDnRem1PtT8It33FoTbSsUEMJCnPZci/15lSz/wGUi lwbPoUgrTekAefoUiejUV5cFb3g9iiPalJrvnc0i//DD6PG6zWXj3wvkSrY4RadIKVhW tmCfVZp2jryu0pEx86fZ5CfMaxpJexfXs7+tuQKWV3uJbujvzLYadQO8WwUbQEA/VrvT Q2RVuNSllLf1O6hc1HILbn4aWBMzyUSy1gvYp4lsgwSxL9yoYNIFPQo72vp0NjOXvyNu XWL1xGF8Kbm51qI95aCRkwXzqeO9DIw69An4VsFaTmPlHLoZpCaECdwW2cHTRO7U1P1o bAPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=a+sBHMOHJhrkJD+T2wbQ+6/KzOArTZmtd+Y1DntHMH0=; b=Wlonk0LnsMKz5HUljqLkHmSRYHzMnphsKZPeAATCvC8bG+6cQ9TP1hwFhPjbtWfNm4 4MNG3vyzqN2KQyLyE4I4k8tYz9xoA988XsHVQwO9tEzK0y/2FPnhgWrbLP40N2th86q0 /vAhfCXMxJVEMCHNPrlQKDwS0WwgM4Ja2Gcb5HuN/hj0s/tcHvlUpHO0u5ofjqgj0BIr vs9M5oRgvmwJedu4QJiOp0BoBt/6qFMymwS1Xq6G/VoIXnGL5MKE2CadjRBgsF/732mn ZE3X16oFyXAWyZXjYMXLGU+kDifzsvQuWi+TpO3v7mJ0hqvr9N60uZKqOgPtkaZXJNFc AJRA== X-Gm-Message-State: APjAAAWlyvL9sRCrcxgf2ChYfzr2WkU8riACUObFNlUUSPk9XGg3kgDw VSxw4JALgVy/72mVl1cRP9DoV0Df4BqteZC9Cxj28sKtL60dltO7TQdqe9ZhINgGVluRfe5Gq+/ Py/Mbh3GONOk4vbHp5CIEHv8G+gCkpso6nTl4P6Hd8AYv9uxXT9Hbsji295haVhxbtupxUHv70c /RdvZf/QeqYA== X-Google-Smtp-Source: APXvYqwbZpKhPquo/tx/F+v6M5gH8l4t62QVQktrvSmW2CTBkk9PMYGtSavByLSab1MDclMS9NtY1w== X-Received: by 2002:a0c:b3c4:: with SMTP id b4mr41272160qvf.176.1558037430792; Thu, 16 May 2019 13:10:30 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([179.56.30.197]) by smtp.gmail.com with ESMTPSA id o37sm4332552qta.86.2019.05.16.13.10.24 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 16 May 2019 13:10:28 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 516411209C5; Thu, 16 May 2019 16:10:22 -0400 (-04) Date: Thu, 16 May 2019 16:10:22 -0400 From: Alvaro Herrera To: "Jonathan S. Katz" , Tom Lane Cc: pgsql-docs@lists.postgresql.org Subject: Re: Documentation for partitioned indexes? Message-ID: <20190516201022.GA15736@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <10560.1556306072@sss.pgh.pa.us> <092b21a2-9579-0f1d-bf22-d6b3db2a8b48@postgresql.org> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit On 2019-Apr-26, Tom Lane wrote: > Alvaro Herrera writes: > > I suppose I better add something in Chapter 5 (DDL), possibly inside the > > 5.10 section (Table Partitioning) -- a new 5.10.6 "Indexes for > > Partitioned Tables" perhaps? > > I was expecting to find it in "5.11.2.2. Partition Maintenance". Here's a first attempt at doing that. I vote to backpatch this to pg11 (since this functionality is all there). > BTW, is there anything equivalent for unique/pkey constraints? > I tried "add constraint unique ... not valid" and just got a > raspberry. Sure, just "alter table only parent", without explicitly marking it not valid. Then the indexes on children must be attached to the parent indexes; this searches for constraints and does the right thing. On 2019-Apr-26, Jonathan S. Katz wrote: > I'd suggest keeping the title of the section similar to the one with > constraints, i.e. "Partitioning and Indexes" In the end, it seemed material far too short to have its own subsection, but maybe if we redesign the whole section we could lay it out differently? (One idea would be to leave 5.11 for declarative partitioning, and add a new section 5.12 for legacy inheritance. Something to think about for pg13) -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services --u3/rZRmxL6MmkK24 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0001-Describe-creation-of-partitioned-index-piecemeal.patch"