Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Uu6gS-0001wP-LB for pgsql-docs@arkaria.postgresql.org; Tue, 02 Jul 2013 19:56:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Uu6gS-0000Hp-4b for pgsql-docs@arkaria.postgresql.org; Tue, 02 Jul 2013 19:56:16 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Uu6gQ-0000GD-Kb for pgsql-docs@postgresql.org; Tue, 02 Jul 2013 19:56:14 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Uu6gO-0000uU-3C for pgsql-docs@postgresql.org; Tue, 02 Jul 2013 19:56:14 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1Uu6gM-0006tE-54; Tue, 02 Jul 2013 15:56:10 -0400 Date: Tue, 2 Jul 2013 15:56:10 -0400 From: Bruce Momjian To: Robert Haas Cc: Craig Ringer , David Johnston , PostgreSQL-documentation Subject: Re: [HACKERS] Add contrib module functions to docs' function index Message-ID: <20130702195610.GD5361@momjian.us> References: <50A2D489.7020102@2ndQuadrant.com> <002101cdc1fa$7c5a2640$750e72c0$@yahoo.com> <50A2E173.6030404@2ndQuadrant.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: 0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Wed, Nov 14, 2012 at 05:46:57PM -0500, Robert Haas wrote: > On Tue, Nov 13, 2012 at 7:10 PM, Craig Ringer wrote: > > I'm talking about making sure that contrib module functions (and settings) > > appear in the documentation index ( > > http://www.postgresql.org/docs/current/static/bookindex.html) so it's easy > > to find a function by name whether it's in core or contrib. This is what I > > want to add to TODO. > > +1. > > > Separately, it might also be nice to add the contrib functions to the > > section 9 tables with an extra column showing their origin, but that's less > > clearly a good thing. Even if there's a column saying "intarray" for > > intarray functions in the array functions list, people will still try to use > > them without loading the extension and get confused when they're not found. > > It'll also bloat the listings of core functions. Rather than do that, I'd > > probably prefer to add a note to relevant sections. For example, in array > > functions I'd want to add "Additional functions that operate only on arrays > > of integers are available in the intarray extension". > > The second approach seems better, and maybe only in cases where it's > particularly relevant. Seems we never considered index entries when we moved the contrib information into our main docs. I have developed the this patch to do this. I would like to apply this to head and 9.3: http://momjian.us/expire/contrib.diff -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs