Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TYljY-0005OF-Nw for pgsql-hackers@postgresql.org; Wed, 14 Nov 2012 22:47:00 +0000 Received: from mail-ie0-f174.google.com ([209.85.223.174]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TYljW-0007uf-NN for pgsql-hackers@postgresql.org; Wed, 14 Nov 2012 22:46:59 +0000 Received: by mail-ie0-f174.google.com with SMTP id k13so1413768iea.19 for ; Wed, 14 Nov 2012 14:46:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UsoyizJqc3m9F0ZDTP8CEFZz/fz2yt8iD5olYk00qOE=; b=XAcNU0hrj9ZycfADm55J7LjTe8vhvfyfJlr6Rm/25AU0h4UUPV2zpOKV0tDeglPT5c vnsd4A/aNbzWRQe1XURAZw1T6CNIqA8Pv93QjwkTm5ALaC6onOh8gyal41q56IgpHJw2 NdI6f8DwHqn8SJ6B/3E3byTMi4VhnCT2Wj4I4DcqJs85YGdAmQ+kX2jzzVYat4iWjYgA 5mApi5fftz+iMeFvxOmtmajX/gH8GHVbhRuFK+p0/SuMXPysZefeey4V9vAVXnD4kpmN xQqRy9+tJ+l2sJwvHuG1RQv3PKBzifcBjNyjOmpbdjOLjv9HDDTW50+5dJq4aQglj2aZ Tfdw== MIME-Version: 1.0 Received: by 10.50.169.100 with SMTP id ad4mr808471igc.50.1352933217966; Wed, 14 Nov 2012 14:46:57 -0800 (PST) Received: by 10.64.23.241 with HTTP; Wed, 14 Nov 2012 14:46:57 -0800 (PST) In-Reply-To: <50A2E173.6030404@2ndQuadrant.com> References: <50A2D489.7020102@2ndQuadrant.com> <002101cdc1fa$7c5a2640$750e72c0$@yahoo.com> <50A2E173.6030404@2ndQuadrant.com> Date: Wed, 14 Nov 2012 17:46:57 -0500 Message-ID: Subject: Re: Add contrib module functions to docs' function index From: Robert Haas To: Craig Ringer Cc: David Johnston , PostgreSQL Hackers Content-Type: text/plain; charset=ISO-8859-1 X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201211/669 X-Sequence-Number: 216521 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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company