Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fvNvt-0000xQ-Tn for pgsql-docs@arkaria.postgresql.org; Thu, 30 Aug 2018 14:28:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fvNvs-0003Xs-42 for pgsql-docs@arkaria.postgresql.org; Thu, 30 Aug 2018 14:28:24 +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.89) (envelope-from ) id 1fvNvr-0003Xl-US for pgsql-docs@lists.postgresql.org; Thu, 30 Aug 2018 14:28:23 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fvNvo-0001Gj-Us for pgsql-docs@postgresql.org; Thu, 30 Aug 2018 14:28:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w7UESIvX006819; Thu, 30 Aug 2018 10:28:18 -0400 From: Tom Lane To: Flavio Henrique Araque Gurgel cc: pgsql-docs@postgresql.org Subject: Re: Limitation of prepared statement name In-reply-to: References: <28416.1535473275@sss.pgh.pa.us> Comments: In-reply-to Flavio Henrique Araque Gurgel message dated "Thu, 30 Aug 2018 16:23:14 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <6817.1535639298.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Thu, 30 Aug 2018 10:28:18 -0400 Message-ID: <6818.1535639298@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Flavio Henrique Araque Gurgel writes: > Em ter, 28 de ago de 2018 às 18:21, Tom Lane escreveu: >> You could as well argue that every single page that describes creating >> any sort of object ought to repeat this information. I doubt that people >> would find that to be an improvement. > I'll never argue repeating the same information everywhere in the docs but > a good solution would be to link the identifiers section everytime an > identifier is used in the docs. That seems like an impossible level of clutter, too. regards, tom lane