Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ej998-00082D-Kl for pgsql-docs@arkaria.postgresql.org; Tue, 06 Feb 2018 19:43:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ej996-0005DK-Rp for pgsql-docs@arkaria.postgresql.org; Tue, 06 Feb 2018 19:43:12 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ej996-0005D8-ME for pgsql-docs@lists.postgresql.org; Tue, 06 Feb 2018 19:43:12 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ej993-0002Nv-0c for pgsql-docs@lists.postgresql.org; Tue, 06 Feb 2018 19:43:11 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id A6EA720BBE; Tue, 6 Feb 2018 14:43:06 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 06 Feb 2018 14:43:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=2/Tjm5 p5+ROZaGR3cp9g2TXm3HFyMsZuaLm0qgE1GzQ=; b=deIoODf17uklihCtUtllxg ulu3vOTh4smYhqYkPMGuvvomcoxvfBuGqOAucPfxvnDjnGQPCLufMPMcb3DLtM0v WpH0hqK/Scc5biQ7ViKPV3J2+epMXPVxpH5DYgbdR7ae8oCHf8lCiT0f5SfTiiIF QIR2Fyjq3zOVDiPbjwAB566FhRCH5cFtnpbRw7/gQqWG+PEVvvB0SL+KFth1RyFt LEj0rIBgEldFMgOZjdrQhcSsvHeOevrRDKLJ94a09/zohzpNcJaaUhUZusF0ca4p qqburSKb86tYPfGTyolMF0S+ifbYXpNGlsXRm9AO5SymkQXEfYb4HrWPVdf8TL6Q == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 5DBCF7E125; Tue, 6 Feb 2018 14:43:06 -0500 (EST) Subject: Re: Pushing btree opclass implementor's docs to the main SGML docs To: Tom Lane , pgsql-docs@lists.postgresql.org References: <23141.1517874668@sss.pgh.pa.us> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <71530296-e555-6bca-49d0-f3361aa883f4@2ndquadrant.com> Date: Tue, 6 Feb 2018 14:43:05 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <23141.1517874668@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/5/18 18:51, Tom Lane wrote: > So I can see two ways to approach this: add two new subsections at the end > of xindex.sgml, or create a new chapter about b-trees in Part VII > ("Internals") to go beside the existing ones about the more recently added > index types. The latter would make more sense if anyone was inspired to > write something comparable in length to the existing per-index-type > chapters. But I'm not volunteering to do that, so if it's a chapter it'd > be a mighty thin one to start with. xindex seems better to me. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services