Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgtPC-0006i4-Mn for pgsql-docs@arkaria.postgresql.org; Thu, 04 Jun 2020 17:11:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jgtPB-0005AL-Jq for pgsql-docs@arkaria.postgresql.org; Thu, 04 Jun 2020 17:11:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgtPB-0005AE-EE for pgsql-docs@lists.postgresql.org; Thu, 04 Jun 2020 17:11:49 +0000 Received: from forward2-smtp.messagingengine.com ([66.111.4.226]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jgtP7-0007Xa-Vm for pgsql-docs@postgresql.org; Thu, 04 Jun 2020 17:11:48 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id 8877B1941BAD; Thu, 4 Jun 2020 13:11:43 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 04 Jun 2020 13:11:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=RHoPlz60PcnDk3RKICntOHVVfVvzszNi1r5NK4Yxt 30=; b=SZDHWMKOaWRy9dsiJlgeMXnRmn0aJguXwurdKtD8b4uOxaNm1zwgHAeM+ iBOWv+Wa0X+61DNymrUtBuO2V9ighjt9ZDlNOpc5ayF58lM2jeE/mZBI1DYzXHSY QP8PhxmvQDSuS/1BbZQeJ4SJ8UDdRKLprOm6D8v+xliaphKlmx9AR//MH65cnH/I rGM84JtvN88XMNmIIhRUapRgkTUvvEdVeygaH0vKXCPn3ZJYIGrgTpiJGWRoYl8s 7spqA2lY6ENpyEgyhs4J4eg9D2wv2jEjBZZ6zVnAdycxPF50aCla5UYLKa+a1t3P iyIl11fuMt4Cu3hKXmnbLX/lLu27g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudeguddguddtudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefuvfhfhfhokffffgggjggtgfesthejredttdefjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsedvnh guqhhurggurhgrnhhtrdgtohhmqeenucggtffrrghtthgvrhhnpedtveeghedtjedvvedv leejueevjeejtdellefgkeelfeeikeejlefgkedtudeuvdenucffohhmrghinhepvdhnug hquhgrughrrghnthdrtghomhenucfkphepleefrddvgeefrdekvddrvdegieenucevlhhu shhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvih hsvghnthhrrghuthesvdhnughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p5df352f6.dip0.t-ipconnect.de [93.243.82.246]) by mail.messagingengine.com (Postfix) with ESMTPA id 23945328005E; Thu, 4 Jun 2020 13:11:42 -0400 (EDT) Subject: Re: Adding xreflable To: Alvaro Herrera , Bruce Momjian References: <20200603223814.GA7455@alvherre.pgsql> Cc: Tom Lane , PostgreSQL-documentation From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <928c6fe4-ae7d-eea2-92ef-ff48f13f060e@2ndquadrant.com> Date: Thu, 4 Jun 2020 19:11:41 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20200603223814.GA7455@alvherre.pgsql> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-06-04 00:38, Alvaro Herrera wrote: > On 2020-Jun-02, Bruce Momjian wrote: > >> I can adjust things, but what logic are we following? Before my patch, >> sepgsql had an xreflabel, and vacuumlo did not. I would like to have a >> documented policy of where we should have xreflabels, and where not, and >> I can then adjust things to match. I don't mind using but it is >> confusing to be able to reference xreflabels in some places and be >> required to use link in others. > > I think a possible rationale would be to *not* include xreflabel for > elements that get numbered (so references become, e.g., "see Section 32.5"), > and include them for those that don't -- so that they can be referenced > at all. Yes, basically everything that already has a generated label doesn't need an xreflabel. Also, if you apply xreflabels somewhere, it needs to be done consistently across all siblings, so you don't get a different style of text depending on which section you happen to link to. And moreover, there should be some general utility for the xreflabel, not just the linking needs of one particular source location. The xreflabels used for the GUC variables are good examples of all three of those points. Generally, xreflabels are a bit of antipattern IMO, so there need to be solid arguments in favor of adding more. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services