Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 860E8633806 for ; Thu, 7 May 2009 10:44:23 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 20202-09 for ; Thu, 7 May 2009 10:44:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by mail.postgresql.org (Postfix) with ESMTP id 3F16B633726 for ; Thu, 7 May 2009 10:44:22 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id E5B18DCC954; Thu, 7 May 2009 15:44:19 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mha-laptop.hagander.net (Postfix) with ESMTP id 4469312449B; Thu, 7 May 2009 15:44:19 +0200 (CEST) Message-ID: <4A02E5B2.5030001@hagander.net> Date: Thu, 07 May 2009 15:44:18 +0200 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: Alvaro Herrera CC: Tom Lane , =?ISO-8859-1?Q?Robert_Gravsj=F6?= , liuzg4 liuzg4 , pgsql-docs@postgresql.org Subject: Re: [GENERAL] how to select temp table References: <4A01CFE8.9010005@blogg.se> <20090506192354.GK4476@alvh.no-ip.org> <20090506192728.GL4476@alvh.no-ip.org> <27338.1241642808@sss.pgh.pa.us> <20090506205307.GM4476@alvh.no-ip.org> <27900.1241644298@sss.pgh.pa.us> <20090506211933.GO4476@alvh.no-ip.org> In-Reply-To: <20090506211933.GO4476@alvh.no-ip.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200905/8 X-Sequence-Number: 5169 Alvaro Herrera wrote: > Tom Lane escribió: >> Alvaro Herrera writes: >>> Hmm, we have another problem then, which is that GUC vars are not >>> showing in the search results when you search for their names. For >>> example if I search for search_path I am suggested >>> http://www.postgresql.org/docs/current/static/ddl-schemas.html#DDL-SCHEMAS-PATH >>> but nothing else. >>> Oh, I see the problem .. the index entry is "search_path configuration >>> parameter". I think it would be better if it were >>> search_pathconfiguration parameter >> Seems like what you are describing is a bug in the search engine, >> not a problem we must address by doubling the vertical space needed for >> literally hundreds of index entries. > > Yeah, perhaps ... I think it should suggest all index entries that > start with the search string, not necessarily equal. > > Magnus? :-) Uh, I don't think that information is even available at that point. We index only the output of the web pages, not the SGML source. //Magnus